From: patchwork-bot+bluetooth@kernel.org
To: Zijun Hu <quic_zijuhu@quicinc.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
abhishekpandit@chromium.org
Subject: Re: [PATCH v2] Bluetooth: Devcoredump: Fix storing u32 without specifying byte order issue
Date: Mon, 17 Apr 2023 18:30:19 +0000 [thread overview]
Message-ID: <168175621934.2755.15515767143213123834.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1681724399-28292-1-git-send-email-quic_zijuhu@quicinc.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 17 Apr 2023 17:39:59 +0800 you wrote:
> API hci_devcd_init() stores its u32 type parameter @dump_size into
> skb, but it does not specify which byte order is used to store the
> integer, let us take little endian to store and parse the integer.
>
> Fixes: f5cc609d09d4 ("Bluetooth: Add support for hci devcoredump")
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: Devcoredump: Fix storing u32 without specifying byte order issue
https://git.kernel.org/bluetooth/bluetooth-next/c/61cad9af36db
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:[~2023-04-17 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 11:49 [PATCH v1] Bluetooth: Optimize devcoredump API hci_devcd_init() Zijun Hu
2023-04-14 21:03 ` Luiz Augusto von Dentz
2023-04-17 9:39 ` [PATCH v2] Bluetooth: Devcoredump: Fix storing u32 without specifying byte order issue Zijun Hu
2023-04-17 18:30 ` patchwork-bot+bluetooth [this message]
2023-04-17 18:30 ` [PATCH v1] Bluetooth: Optimize devcoredump API hci_devcd_init() patchwork-bot+bluetooth
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=168175621934.2755.15515767143213123834.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_zijuhu@quicinc.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
all inboxes | Powered by JetHome®