Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btmrvl: Slightly simplify btmrvl_process_event()
Date: Tue, 11 Aug 2026 20:10:16 +0000	[thread overview]
Message-ID: <178647901638.1134064.11068841351283919495.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9fc342cc7dd726868216174cd83d196d1ca18f94.1786280385.git.christophe.jaillet@wanadoo.fr>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Sun,  9 Aug 2026 14:59:59 +0200 you wrote:
> In btmrvl_process_event(), all error handling paths except one do a direct
> return. Update the only one that makes a goto to be consistent.
> 
> This does not change the behavior because ret is known to be != 0 when
> 'exit' is reached.
> 
> This simplifies the code, saves 2 LoC and pleases one of my coccinelle
> script that tries to spot erroneously mixed goto and return statements.
> 
> [...]

Here is the summary with links:
  - Bluetooth: btmrvl: Slightly simplify btmrvl_process_event()
    https://git.kernel.org/bluetooth/bluetooth-next/c/b2d457736260

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-11 20:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09 12:59 [PATCH] Bluetooth: btmrvl: Slightly simplify btmrvl_process_event() Christophe JAILLET
2026-08-09 14:02 ` bluez.test.bot
2026-08-11 20:10 ` patchwork-bot+bluetooth [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=178647901638.1134064.11068841351283919495.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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