From: patchwork-bot+ofono@kernel.org
To: Steve Schrock <steve.schrock@getcruise.com>
Cc: ofono@lists.linux.dev
Subject: Re: [PATCH] qmimodem: QRTR service discovery
Date: Tue, 27 Feb 2024 22:10:30 +0000 [thread overview]
Message-ID: <170907183006.24151.4324200142058751835.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227210143.142603-1-steve.schrock@getcruise.com>
Hello:
This patch was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Tue, 27 Feb 2024 21:01:43 +0000 you wrote:
> QRTR service discovery works by sending QRTR_TYPE_NEW_LOOKUP to
> the special socket of type AF_QIPCRTR. Then the services are received
> one-by-one. Soon they will be stored and made available for use by the
> qmi client.
>
> There was a re-entrancy problem where the qmi_device could be
> destroyed in a callback, but then the code running would still try
> to access that device. This was solved by creating a common macro
> that would do things in the right order so that the qmi_device was
> not accessed again after calling back into the client.
>
> [...]
Here is the summary with links:
- qmimodem: QRTR service discovery
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=ffebc1ffa6de
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-02-27 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 21:01 [PATCH] qmimodem: QRTR service discovery Steve Schrock
2024-02-27 22:10 ` patchwork-bot+ofono [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 17:12 Steve Schrock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170907183006.24151.4324200142058751835.git-patchwork-notify@kernel.org \
--to=patchwork-bot+ofono@kernel.org \
--cc=ofono@lists.linux.dev \
--cc=steve.schrock@getcruise.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).