From: Andrew Morton <akpm@linux-foundation.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Hemant Kumar <hemantk@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH -next/-mmotm] bus/mhi: fix printk format for size_t
Date: Mon, 23 Mar 2020 19:24:27 -0700 [thread overview]
Message-ID: <20200323192427.5903a6224ec85a07bd976c13@linux-foundation.org> (raw)
In-Reply-To: <20200322044952.GA17141@Mani-XPS-13-9360>
On Sun, 22 Mar 2020 10:19:52 +0530 Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> wrote:
> On Sat, Mar 21, 2020 at 09:17:52PM -0700, Randy Dunlap wrote:
> > From: Randy Dunlap <rdunlap@infradead.org>
> >
> > Fix printk format warning by using %z for size_t modifier:
> >
> > ../drivers/bus/mhi/core/boot.c: In function ‘mhi_rddm_prepare’:
> > ../drivers/bus/mhi/core/boot.c:55:15: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 5 has type ‘size_t {aka unsigned int}’ [-Wformat=]
> > dev_dbg(dev, "Address: %p and len: 0x%lx sequence: %u\n",
> >
> >
> > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>
> Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Thanks. I guess we should tell Greg, who presently holds the offending
patch. I shall add
Fixes: 6fdfdd27328ce ("bus: mhi: core: Add support for downloading RDDM image du
ring panic")
and send it over.
prev parent reply other threads:[~2020-03-24 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 4:17 [PATCH -next/-mmotm] bus/mhi: fix printk format for size_t Randy Dunlap
2020-03-22 4:49 ` Manivannan Sadhasivam
2020-03-24 2:24 ` Andrew Morton [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=20200323192427.5903a6224ec85a07bd976c13@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).