All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Nathan Chancellor <nathan@kernel.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	sean.wang@mediatek.com, chris.lu@mediatek.com,
	matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
	linux-bluetooth@vger.kernel.org,
	linux-mediatek@lists.infradead.org, patches@lists.linux.dev
Subject: Re: [PATCH bluetooth-next] Bluetooth: btmtk: Mark all stub functions as inline
Date: Mon, 15 Jul 2024 01:30:29 +0000	[thread overview]
Message-ID: <172100702902.7085.5923916959571954245.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240710-btmtk-add-missing-inline-to-stubs-v1-1-ba33143ee148@kernel.org>

Hello:

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

On Wed, 10 Jul 2024 10:56:24 -0700 you wrote:
> Several recent patches added static stubs to btmtk.h without the inline
> keyword, which causes instances of -Wunused-function when those stubs
> are not used anywhere in a file that includes the header:
> 
>   In file included from drivers/bluetooth/btusb.c:28:
>   drivers/bluetooth/btmtk.h:254:13: warning: 'btmtk_fw_get_filename' defined but not used [-Wunused-function]
>     254 | static void btmtk_fw_get_filename(char *buf, size_t size, u32 dev_id,
>         |             ^~~~~~~~~~~~~~~~~~~~~
>   drivers/bluetooth/btmtk.h:249:12: warning: 'btmtk_process_coredump' defined but not used [-Wunused-function]
>     249 | static int btmtk_process_coredump(struct hci_dev *hdev, struct sk_buff *skb)
>         |            ^~~~~~~~~~~~~~~~~~~~~~
>   drivers/bluetooth/btmtk.h:243:12: warning: 'btmtk_register_coredump' defined but not used [-Wunused-function]
>     243 | static int btmtk_register_coredump(struct hci_dev *hdev, const char *name,
>         |            ^~~~~~~~~~~~~~~~~~~~~~~
>   drivers/bluetooth/btmtk.h:233:12: warning: 'btmtk_setup_firmware' defined but not used [-Wunused-function]
>     233 | static int btmtk_setup_firmware(struct hci_dev *hdev, const char *fwname,
>         |            ^~~~~~~~~~~~~~~~~~~~
>   drivers/bluetooth/btmtk.h:227:12: warning: 'btmtk_setup_firmware_79xx' defined but not used [-Wunused-function]
>     227 | static int btmtk_setup_firmware_79xx(struct hci_dev *hdev, const char *fwname,
>         |            ^~~~~~~~~~~~~~~~~~~~~~~~~
> 
> [...]

Here is the summary with links:
  - [bluetooth-next] Bluetooth: btmtk: Mark all stub functions as inline
    https://git.kernel.org/bluetooth/bluetooth-next/c/cebba8aa58ab

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



      parent reply	other threads:[~2024-07-15  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10 17:56 [PATCH bluetooth-next] Bluetooth: btmtk: Mark all stub functions as inline Nathan Chancellor
2024-07-10 18:39 ` [bluetooth-next] " bluez.test.bot
2024-07-15  1: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=172100702902.7085.5923916959571954245.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chris.lu@mediatek.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nathan@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=sean.wang@mediatek.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.