From: Francesco Dolcini <francesco@dolcini.it>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Stefan Eichenberger <stefan.eichenberger@toradex.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: [PATCH v3 3/5] Bluetooth: hci_mrvl: use maybe_unused macro for device tree ids
Date: Mon, 13 Feb 2023 13:09:24 +0100 [thread overview]
Message-ID: <20230213120926.8166-4-francesco@dolcini.it> (raw)
In-Reply-To: <20230213120926.8166-1-francesco@dolcini.it>
From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
Use the maybe_unused macro for the device tree ids instead of #ifdef
CONFIG_OF. This makes it easier to add support for new devices.
Signed-off-by: Stefan Eichenberger <stefan.eichenberger@toradex.com>
Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
---
v3: no changes
v2: new patch
---
drivers/bluetooth/hci_mrvl.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/bluetooth/hci_mrvl.c b/drivers/bluetooth/hci_mrvl.c
index fbc3f7c3a5c7..eaa9c51cacfa 100644
--- a/drivers/bluetooth/hci_mrvl.c
+++ b/drivers/bluetooth/hci_mrvl.c
@@ -414,13 +414,11 @@ static void mrvl_serdev_remove(struct serdev_device *serdev)
hci_uart_unregister_device(&mrvldev->hu);
}
-#ifdef CONFIG_OF
-static const struct of_device_id mrvl_bluetooth_of_match[] = {
+static const struct of_device_id __maybe_unused mrvl_bluetooth_of_match[] = {
{ .compatible = "mrvl,88w8897" },
{ },
};
MODULE_DEVICE_TABLE(of, mrvl_bluetooth_of_match);
-#endif
static struct serdev_device_driver mrvl_serdev_driver = {
.probe = mrvl_serdev_probe,
--
2.25.1
next prev parent reply other threads:[~2023-02-13 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 12:09 [PATCH v3 0/5] Bluetooth: hci_mrvl: Add serdev support for 88W8997 Francesco Dolcini
2023-02-13 12:09 ` [PATCH v3 1/5] dt-bindings: bluetooth: marvell: add 88W8997 Francesco Dolcini
2023-02-13 12:09 ` [PATCH v3 2/5] dt-bindings: bluetooth: marvell: add max-speed property Francesco Dolcini
2023-02-13 12:09 ` Francesco Dolcini [this message]
2023-02-13 12:09 ` [PATCH v3 4/5] Bluetooth: hci_mrvl: Add serdev support for 88W8997 Francesco Dolcini
2023-02-13 12:09 ` [PATCH v3 5/5] arm64: dts: imx8mp-verdin: add 88W8997 serdev to uart4 Francesco Dolcini
2023-02-16 8:49 ` Francesco Dolcini
2023-03-13 14:05 ` Shawn Guo
2023-02-15 20:36 ` [PATCH v3 0/5] Bluetooth: hci_mrvl: Add serdev support for 88W8997 Luiz Augusto von Dentz
2023-02-15 20:41 ` Francesco Dolcini
2023-02-15 21:20 ` 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=20230213120926.8166-4-francesco@dolcini.it \
--to=francesco@dolcini.it \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=francesco.dolcini@toradex.com \
--cc=johan.hedberg@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=stefan.eichenberger@toradex.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
all inboxes | Powered by JetHome®