From: patchwork-bot+ofono@kernel.org
To: Steve Schrock <steve.schrock@getcruise.com>
Cc: ofono@lists.linux.dev
Subject: Re: [PATCH v3 1/2] qmi: Separate the pending family creation queues
Date: Tue, 07 May 2024 17:00:27 +0000 [thread overview]
Message-ID: <171510122798.14353.9080094163650157369.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240507160353.683868-1-steve.schrock@getcruise.com>
Hello:
This series was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Tue, 7 May 2024 11:03:47 -0500 you wrote:
> The family_list hashmap is keyed by the client ID and service type,
> unless qmux is creating the first client for a service type. In that
> case the high bytes are 0x8000 instead of the client ID, and the
> value is a queue of clients waiting for that service instead of the
> service_family.
>
> This commit moves the pending clients into thir own hashmap to ensure
> that each hashmap contains a consistent type and eliminates the need
> for marking pending keys with 0x80000000.
>
> [...]
Here is the summary with links:
- [v3,1/2] qmi: Separate the pending family creation queues
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=2f11471e0dd7
- [v3,2/2] qmi: Move the pending queues into qmi_device_qmux
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=309b7b263d1c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-05-07 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 16:03 [PATCH v3 1/2] qmi: Separate the pending family creation queues Steve Schrock
2024-05-07 16:03 ` [PATCH v3 2/2] qmi: Move the pending queues into qmi_device_qmux Steve Schrock
2024-05-07 17:00 ` patchwork-bot+ofono [this message]
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=171510122798.14353.9080094163650157369.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).