From: Wei Yongjun <weiyongjun@huaweicloud.com>
To: Pavel Machek <pavel@ucw.cz>, Oleh Kravchenko <oleg@kaa.org.ua>
Cc: Wei Yongjun <weiyongjun1@huawei.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] leds: el15203000: silent no spi_device_id warning
Date: Mon, 5 Sep 2022 15:26:58 +0000 [thread overview]
Message-ID: <20220905152659.4152483-2-weiyongjun@huaweicloud.com> (raw)
In-Reply-To: <20220905152659.4152483-1-weiyongjun@huaweicloud.com>
From: Wei Yongjun <weiyongjun1@huawei.com>
Add spi_device_id entries to silent following SPI warning:
SPI driver leds_el15203000 has no spi_device_id for crane,el15203000
Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
---
drivers/leds/leds-el15203000.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/leds/leds-el15203000.c b/drivers/leds/leds-el15203000.c
index 7e7b617bcd56..e24b4399176e 100644
--- a/drivers/leds/leds-el15203000.c
+++ b/drivers/leds/leds-el15203000.c
@@ -329,9 +329,16 @@ static const struct of_device_id el15203000_dt_ids[] = {
MODULE_DEVICE_TABLE(of, el15203000_dt_ids);
+static const struct spi_device_id el15203000_spi_ids[] = {
+ { "el15203000" },
+ { },
+};
+MODULE_DEVICE_TABLE(spi, el15203000_spi_ids);
+
static struct spi_driver el15203000_driver = {
.probe = el15203000_probe,
.remove = el15203000_remove,
+ .id_table = el15203000_spi_ids,
.driver = {
.name = KBUILD_MODNAME,
.of_match_table = el15203000_dt_ids,
--
2.34.1
next prev parent reply other threads:[~2022-09-05 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 15:26 [PATCH 1/3] leds: cr0014114: silent no spi_device_id warning Wei Yongjun
2022-09-05 15:26 ` Wei Yongjun [this message]
2022-09-05 20:53 ` [PATCH 2/3] leds: el15203000: " Oleh Kravchenko
2022-09-05 15:26 ` [PATCH 3/3] leds: spi-byte: " Wei Yongjun
2022-09-05 20:53 ` [PATCH 1/3] leds: cr0014114: " Oleh Kravchenko
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=20220905152659.4152483-2-weiyongjun@huaweicloud.com \
--to=weiyongjun@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=oleg@kaa.org.ua \
--cc=pavel@ucw.cz \
--cc=weiyongjun1@huawei.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;
as well as URLs for NNTP newsgroup(s).