From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Arnd Bergmann <arnd@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Christophe Kerello <christophe.kerello@foss.st.com>,
Zhang Qilong <zhangqilong3@huawei.com>,
linux-spi <linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: stm32-qspi: fix debug format string
Date: Thu, 22 Apr 2021 09:30:16 +0200 [thread overview]
Message-ID: <b970a557-b869-c867-3825-370a36feef68@foss.st.com> (raw)
In-Reply-To: <CAK8P3a0CWp_H-tm2QcZyH1FDXwzMgxY_9dc1Y8pA28MQKT-q=A@mail.gmail.com>
Hi Mark, Arnd
Regarding this issue, how do you prefer to proceed ?
Patrice
On 4/21/21 5:22 PM, Arnd Bergmann wrote:
> On Wed, Apr 21, 2021 at 5:05 PM Mark Brown <broonie@kernel.org> wrote:
>>
>> On Wed, Apr 21, 2021 at 04:06:48PM +0200, Arnd Bergmann wrote:
>>> From: Arnd Bergmann <arnd@arndb.de>
>>>
>>> Printing size_t needs a special %zd format modifier to avoid a
>>> warning like:
>>
>> This doesn't apply against current code, please check and resend.
>
> It appears that you just applied 1b8a7d4282c0 ("spi: stm32-qspi:
> Fix compilation warning in ARM64") after today's linux-next was
> cut.
>
> I suspect Patrice's patch now causes a warning on all architectures
> on which size_t is defined as 'unsigned int'.
>
> Arnd
>
next prev parent reply other threads:[~2021-04-22 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 14:06 Arnd Bergmann
2021-04-21 15:05 ` Mark Brown
2021-04-21 15:22 ` Arnd Bergmann
2021-04-22 7:30 ` Patrice CHOTARD [this message]
2021-04-22 11:32 ` Mark Brown
2021-04-22 16:48 ` Mark Brown
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=b970a557-b869-c867-3825-370a36feef68@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@kernel.org \
--cc=broonie@kernel.org \
--cc=christophe.kerello@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=zhangqilong3@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
all inboxes | Powered by JetHome®