All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Zijun Hu <quic_zijuhu@quicinc.com>
Cc: luiz.dentz@gmail.com, pmenzel@molgen.mpg.de,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] main: Fix integer configuration option parse failures
Date: Mon, 31 Jul 2023 17:50:24 +0000	[thread overview]
Message-ID: <169082582439.13999.13820304183162328350.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1690795722-29873-1-git-send-email-quic_zijuhu@quicinc.com>

Hello:

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

On Mon, 31 Jul 2023 17:28:42 +0800 you wrote:
> parse_config_int() has a obvious logical error, so causes many
> parse failures of integer configuration options, fixed by this
> change.
> ---
>  src/main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Here is the summary with links:
  - [BlueZ,v2] main: Fix integer configuration option parse failures
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=446d8ada5790

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



  parent reply	other threads:[~2023-07-31 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  7:46 [PATCH v1] main: Fix a logical error within parse_config_int() Zijun Hu
2023-07-31  8:48 ` Paul Menzel
2023-07-31  8:58   ` quic_zijuhu
2023-07-31  9:16 ` [v1] " bluez.test.bot
2023-07-31  9:28 ` [PATCH BlueZ v2] main: Fix integer configuration option parse failures Zijun Hu
2023-07-31 10:46   ` [BlueZ,v2] " bluez.test.bot
2023-07-31 17:50   ` patchwork-bot+bluetooth [this message]
2023-07-31 17:50 ` [PATCH v1] main: Fix a logical error within parse_config_int() 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=169082582439.13999.13820304183162328350.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=pmenzel@molgen.mpg.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.