From: Linus Walleij <linus.walleij@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Vladimir Zapolskiy <vz@mleia.com>,
Sylvain Lemieux <slemieux.tyco@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>, Jean Delvare <jdelvare@suse.de>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Max Staudt <max@enpas.org>,
Juergen Fitschen <jfi@ssv-embedded.de>,
Elie Morisse <syniurge@gmail.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/5] i2c: stu300: Use proper printk format for iomem pointer
Date: Tue, 7 Jan 2020 11:36:04 +0100 [thread overview]
Message-ID: <CACRpkdaKPWott93XQp1iWMO6m6TqqW+iuN33PnSDOnOMMdCEbg@mail.gmail.com> (raw)
In-Reply-To: <20191230172751.17985-4-krzk@kernel.org>
On Mon, Dec 30, 2019 at 6:28 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> iomem pointers should be printed with pointer format to hide the
> actual value and fix warnings when compiling on 64-bit platform (e.g. with
> COMPILE_TEST):
>
> drivers/i2c/busses/i2c-stu300.c: In function ‘stu300_wait_while_busy’:
> drivers/i2c/busses/i2c-stu300.c:446:76: warning:
> cast from pointer to integer of different size [-Wpointer-to-int-cast]
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-01-07 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 17:27 [PATCH 1/5] i2c: pmcmsp: Use proper printk format for resource_size_t Krzysztof Kozlowski
2019-12-30 17:27 ` [PATCH 2/5] i2c: pnx: " Krzysztof Kozlowski
2019-12-30 17:27 ` [PATCH 3/5] i2c: highlander: Use proper printk format for iomem pointer Krzysztof Kozlowski
2020-01-07 15:08 ` Luca Ceresoli
2019-12-30 17:27 ` [PATCH 4/5] i2c: stu300: " Krzysztof Kozlowski
2020-01-07 10:36 ` Linus Walleij [this message]
2019-12-30 17:27 ` [PATCH 5/5] i2c: Enable compile testing for some of drivers Krzysztof Kozlowski
2019-12-30 19:11 ` Geert Uytterhoeven
2019-12-31 9:01 ` Krzysztof Kozlowski
2019-12-31 9:20 ` Geert Uytterhoeven
2020-01-03 13:42 ` Krzysztof Kozlowski
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=CACRpkdaKPWott93XQp1iWMO6m6TqqW+iuN33PnSDOnOMMdCEbg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=jfi@ssv-embedded.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@enpas.org \
--cc=slemieux.tyco@gmail.com \
--cc=syniurge@gmail.com \
--cc=vz@mleia.com \
--cc=wsa@the-dreams.de \
/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).