From: patchwork-bot+bluetooth@kernel.org
To: Sasha Finkelstein via B4 Relay
<devnull+fnkl.kernel.gmail.com@kernel.org>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
fnkl.kernel@gmail.com
Subject: Re: [PATCH RESEND] bluetooth: btbcm: Fix logic error in forming the board name.
Date: Tue, 14 Mar 2023 23:10:21 +0000 [thread overview]
Message-ID: <167883542103.4543.14888292350332012679.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230224-btbcm-wtf-v1-1-98b56133a5b7@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 10 Mar 2023 11:28:42 +0100 you wrote:
> From: Sasha Finkelstein <fnkl.kernel@gmail.com>
>
> This patch fixes an incorrect loop exit condition in code that replaces
> '/' symbols in the board name. There might also be a memory corruption
> issue here, but it is unlikely to be a real problem.
>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Sasha Finkelstein <fnkl.kernel@gmail.com>
>
> [...]
Here is the summary with links:
- [RESEND] bluetooth: btbcm: Fix logic error in forming the board name.
https://git.kernel.org/bluetooth/bluetooth-next/c/3629e1ce7721
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-03-14 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 10:28 [PATCH RESEND] bluetooth: btbcm: Fix logic error in forming the board name Sasha Finkelstein via B4 Relay
2023-03-14 23:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-10 8:07 Sasha Finkelstein via B4 Relay
2023-03-10 8:10 ` Greg KH
2023-03-10 9:41 ` Sasha Finkelstein
2023-03-10 9:53 ` Greg KH
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=167883542103.4543.14888292350332012679.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=devnull+fnkl.kernel.gmail.com@kernel.org \
--cc=fnkl.kernel@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
/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