linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>,
	Dinh Nguyen <dinguyen@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] clk: socfpga: fix iomem pointer cast on 64-bit
Date: Fri, 09 Apr 2021 10:02:16 -0700	[thread overview]
Message-ID: <161798773615.3790633.4877613255691338405@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <161795309623.1751103.16552528876108968953.b4-ty@arndb.de>

Quoting Arnd Bergmann (2021-04-09 00:26:50)
> From: Arnd Bergmann <arnd@arndb.de>
> 
> On Sun, 14 Mar 2021 12:07:09 +0100, Krzysztof Kozlowski wrote:
> > Pointers should be cast with uintptr_t instead of integer.  This fixes
> > warning when compile testing on ARM64:
> > 
> >   drivers/clk/socfpga/clk-gate.c: In function ‘socfpga_clk_recalc_rate’:
> >   drivers/clk/socfpga/clk-gate.c:102:7: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> 
> I decided to pull that into the arm/drivers branch as well, to avoid the
> build regression. Since the same fix is in the clk tree, there will now
> be a duplicated commit in the git history, but I prefer that over introducing
> warnings.
> 
> [1/1] clk: socfpga: fix iomem pointer cast on 64-bit
>       commit: 36841008059caec9667459a7e126efac6379676b
> 

Ok. I'm sending it off to Linus now.

      reply	other threads:[~2021-04-09 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14 11:07 [PATCH v2] clk: socfpga: fix iomem pointer cast on 64-bit Krzysztof Kozlowski
2021-03-29 19:04 ` Stephen Boyd
2021-04-09  7:26 ` Arnd Bergmann
2021-04-09 17:02   ` Stephen Boyd [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=161798773615.3790633.4877613255691338405@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.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;
as well as URLs for NNTP newsgroup(s).