All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/2] shared/shell: Fix build errors in fc42
Date: Fri, 18 Apr 2025 14:10:35 +0000	[thread overview]
Message-ID: <174498543503.225291.7790404171985405348.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250417202113.80496-1-luiz.dentz@gmail.com>

Hello:

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

On Thu, 17 Apr 2025 16:21:12 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This fixes the following errors:
> 
> src/shared/shell.c: In function 'rl_cleanup':
> src/shared/shell.c:1429:20: error: zero-length gnu_printf format string [-Werror=format-zero-length]
>  1429 |         rl_message("");
>       |                    ^~
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1,1/2] shared/shell: Fix build errors in fc42
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e501c8ab3023
  - [BlueZ,v1,2/2] mesh: Fix build errors when compiling on fc42
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2a569ec80ffb

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



      parent reply	other threads:[~2025-04-18 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 20:21 [PATCH BlueZ v1 1/2] shared/shell: Fix build errors in fc42 Luiz Augusto von Dentz
2025-04-17 20:21 ` [PATCH BlueZ v1 2/2] mesh: Fix build errors when compiling on fc42 Luiz Augusto von Dentz
2025-04-17 21:58 ` [BlueZ,v1,1/2] shared/shell: Fix build errors in fc42 bluez.test.bot
2025-04-18 14: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=174498543503.225291.7790404171985405348.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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.