From: patchwork-bot+bluetooth@kernel.org
To: Dr. David Alan Gilbert <linux@treblig.org>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Bluetooth: MGMT: Deadcode cleanup
Date: Tue, 28 Jan 2025 20:30:33 +0000 [thread overview]
Message-ID: <173809623301.3912505.5958977606230134366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250127213716.232551-1-linux@treblig.org>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 27 Jan 2025 21:37:14 +0000 you wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> Hi,
> A couple of deadcode removal patches.
>
> They're both strictly function removals, no internal changes
> to a function.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: MGMT: Remove unused mgmt_pending_find_data
https://git.kernel.org/bluetooth/bluetooth-next/c/f694e720fddd
- [2/2] Bluetooth: MGMT: Remove unused mgmt_*_discovery_complete
https://git.kernel.org/bluetooth/bluetooth-next/c/55b8d4c01dde
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-28 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 21:37 [PATCH 0/2] Bluetooth: MGMT: Deadcode cleanup linux
2025-01-27 21:37 ` [PATCH 1/2] Bluetooth: MGMT: Remove unused mgmt_pending_find_data linux
2025-01-28 16:30 ` Simon Horman
2025-01-27 21:37 ` [PATCH 2/2] Bluetooth: MGMT: Remove unused mgmt_*_discovery_complete linux
2025-01-28 16:30 ` Simon Horman
2025-01-28 20:30 ` 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=173809623301.3912505.5958977606230134366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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