From: Andrew Davis <afd@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Martyn Welch <martyn.welch@collabora.com>,
Hari Nagalla <hnagalla@ti.com>
Cc: <oe-kbuild-all@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] mailbox: ti-msgmgr: Allow building under COMPILE_TEST
Date: Tue, 15 Oct 2024 16:34:34 -0500 [thread overview]
Message-ID: <b6ddbcfa-91ce-4774-b577-08f41e773781@ti.com> (raw)
In-Reply-To: <1a88e7b5-582f-4d52-864a-e828f6619bc8@app.fastmail.com>
On 10/15/24 3:54 PM, Arnd Bergmann wrote:
> Hi Andrew,
>
> On Tue, Oct 15, 2024, at 20:46, kernel test robot wrote:
>> In file included from drivers/firmware/ti_sci.c:14:
>> In file included from include/linux/io.h:14:
>> In file included from arch/hexagon/include/asm/io.h:328:
>> include/asm-generic/io.h:548:31: warning: performing pointer
>> arithmetic on a null pointer has undefined behavior
>> [-Wnull-pointer-arithmetic]
>> 548 | val = __raw_readb(PCI_IOBASE + addr);
>> | ~~~~~~~~~~ ^
>> include/asm-generic/io.h:561:61: warning: performing pointer
>> arithmetic on a null pointer has undefined behavior
>> [-Wnull-pointer-arithmetic]
>> 561 | val = __le16_to_cpu((__le16
>> __force)__raw_readw(PCI_IOBASE + addr));
>> |
>
>
> Hopefully we will be able to finally address these in 6.13
> for all drivers, it's been a decade. Don't worry about
> the above.
>
>
>> platform_device *dev,
>> | ^~~~~~~~~~~~~~~~~~~~~~
>>>> drivers/firmware/ti_sci.c:3285:34: warning: unused variable 'ti_sci_of_match' [-Wunused-const-variable]
>> 3285 | static const struct of_device_id ti_sci_of_match[] = {
>> | ^~~~~~~~~~~~~~~
>> 8 warnings generated.
>>
>
> Needs this change, please fold into your patch.
Was going to clean this up in several places in another series,
but will add this one to this series, v2 on the way.
Andrew
>
> diff --git a/drivers/firmware/ti_sci.c b/drivers/firmware/ti_sci.c
> index 160968301b1f..6a6bf7a2d134 100644
> --- a/drivers/firmware/ti_sci.c
> +++ b/drivers/firmware/ti_sci.c
> @@ -3421,7 +3421,7 @@ static struct platform_driver ti_sci_driver = {
> .probe = ti_sci_probe,
> .driver = {
> .name = "ti-sci",
> - .of_match_table = of_match_ptr(ti_sci_of_match),
> + .of_match_table = ti_sci_of_match,
> .suppress_bind_attrs = true,
> },
> };
>
>
next prev parent reply other threads:[~2024-10-15 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 14:48 [PATCH 0/2] Enable compile testing of TI MSGMGR/SPROXY driver Andrew Davis
2024-10-14 14:48 ` [PATCH 1/2] mailbox: ti-msgmgr: Remove use of of_match_ptr() helper Andrew Davis
2024-10-14 14:52 ` Arnd Bergmann
2024-10-14 14:48 ` [PATCH 2/2] mailbox: ti-msgmgr: Allow building under COMPILE_TEST Andrew Davis
2024-10-14 14:52 ` Arnd Bergmann
2024-10-15 20:46 ` kernel test robot
2024-10-15 20:54 ` Arnd Bergmann
2024-10-15 21:34 ` Andrew Davis [this message]
2024-10-14 16:53 ` [PATCH 0/2] Enable compile testing of TI MSGMGR/SPROXY driver Nishanth Menon
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=b6ddbcfa-91ce-4774-b577-08f41e773781@ti.com \
--to=afd@ti.com \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=hnagalla@ti.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martyn.welch@collabora.com \
--cc=mathieu.poirier@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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