From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com, lkp@intel.com
Subject: Re: [PATCH v1 1/2] Bluetooth: btintel_pcie: Fix warning reported by sparse
Date: Tue, 14 May 2024 14:53:07 +0000 [thread overview]
Message-ID: <171569838792.3449.10440377454024129807.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240511054059.349729-1-kiran.k@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 11 May 2024 11:10:58 +0530 you wrote:
> Fix sparse error.
>
> Fixes: a6c49bbb0b72 ("Bluetooth: btintel_pcie: Add support for PCIe transport")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202405100654.0djvoryZ-lkp@intel.com/
> Signed-off-by: Kiran K <kiran.k@intel.com>
>
> [...]
Here is the summary with links:
- [v1,1/2] Bluetooth: btintel_pcie: Fix warning reported by sparse
https://git.kernel.org/bluetooth/bluetooth-next/c/c5cbf4f0271c
- [v1,2/2] Bluetooth: btintel_pcie: Refactor and code cleanup
https://git.kernel.org/bluetooth/bluetooth-next/c/710dfef50bab
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:[~2024-05-14 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 5:40 [PATCH v1 1/2] Bluetooth: btintel_pcie: Fix warning reported by sparse Kiran K
2024-05-11 5:40 ` [PATCH v1 2/2] Bluetooth: btintel_pcie: Refactor and code cleanup Kiran K
2024-05-11 5:55 ` [v1,1/2] Bluetooth: btintel_pcie: Fix warning reported by sparse bluez.test.bot
2024-05-14 14:53 ` 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=171569838792.3449.10440377454024129807.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ravishankar.srivatsa@intel.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.