From: Nicolas Pitre <nico@fluxnic.net>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Souptick Joarder <jrdr.linux@gmail.com>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
Boris Brezillon <bbrezillon@kernel.org>
Subject: Re: [linux-next:master 6404/13375] drivers/i3c/master/mipi-i3c-hci/core.c:780:34: warning: unused variable 'i3c_hci_of_match'
Date: Wed, 16 Dec 2020 09:44:30 -0500 (EST) [thread overview]
Message-ID: <rrq8n6pn-164s-697p-o538-no5055s8431o@syhkavp.arg> (raw)
In-Reply-To: <20201216094658.67472406@collabora.com>
On Wed, 16 Dec 2020, Boris Brezillon wrote:
> Or adding a __maybe_unused qualifier. Can you send patch for this so I
> can apply it before sending my PR to Linus?
Here it is:
---------- >8
From: Nicolas Pitre <npitre@baylibre.com>
Subject: [PATCH] i3c/master/mipi-i3c-hci: quiet maybe-unused variable warning
If CONFIG_OF is disabled then the matching table is notreferenced.
Reported-by: kernel test robot <lkp@intel.com>
Signed-by: Nicolas Pitre <npitre@baylibre.com>
diff --git a/drivers/i3c/master/mipi-i3c-hci/core.c b/drivers/i3c/master/mipi-i3c-hci/core.c
index 113c4c9054..500abd27fb 100644
--- a/drivers/i3c/master/mipi-i3c-hci/core.c
+++ b/drivers/i3c/master/mipi-i3c-hci/core.c
@@ -777,7 +777,7 @@ static int i3c_hci_remove(struct platform_device *pdev)
return 0;
}
-static const struct of_device_id i3c_hci_of_match[] = {
+static const struct __maybe_unused of_device_id i3c_hci_of_match[] = {
{ .compatible = "mipi-i3c-hci", },
{},
};
prev parent reply other threads:[~2020-12-16 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 20:01 kernel test robot
2020-12-15 19:00 ` Souptick Joarder
2020-12-16 3:28 ` Nicolas Pitre
2020-12-16 8:46 ` Boris Brezillon
2020-12-16 14:44 ` Nicolas Pitre [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=rrq8n6pn-164s-697p-o538-no5055s8431o@syhkavp.arg \
--to=nico@fluxnic.net \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=clang-built-linux@googlegroups.com \
--cc=jrdr.linux@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox