From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>
Cc: Dinh Nguyen <dinguyen@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the arm-soc tree
Date: Tue, 6 Apr 2021 08:34:36 +0200 [thread overview]
Message-ID: <190b8e95-2a96-142e-7b98-34318eea6804@canonical.com> (raw)
In-Reply-To: <20210406104511.2535b830@canb.auug.org.au>
On 06/04/2021 02:45, Stephen Rothwell wrote:
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> 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]
> 102 | if ((int) socfpgaclk->div_reg & SOCFPGA_GPIO_DB_CLK_OFFSET)
> | ^
>
> Exposed by commit
>
> cdb1e8b4f4c2 ("clk: socfpga: allow compile testing of Stratix 10 / Agilex clocks")
> 552418658acd ("clk: socfpga: use ARCH_INTEL_SOCFPGA also for 32-bit ARM SoCs (and compile test)")
>
Thanks Stephen. This is a result of compile testing and was already
fixed via clk tree. You should not have the warning after all the merges.
https://lore.kernel.org/lkml/20210314110709.32599-1-krzysztof.kozlowski@canonical.com/
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>
Cc: Dinh Nguyen <dinguyen@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the arm-soc tree
Date: Tue, 6 Apr 2021 08:34:36 +0200 [thread overview]
Message-ID: <190b8e95-2a96-142e-7b98-34318eea6804@canonical.com> (raw)
In-Reply-To: <20210406104511.2535b830@canb.auug.org.au>
On 06/04/2021 02:45, Stephen Rothwell wrote:
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> 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]
> 102 | if ((int) socfpgaclk->div_reg & SOCFPGA_GPIO_DB_CLK_OFFSET)
> | ^
>
> Exposed by commit
>
> cdb1e8b4f4c2 ("clk: socfpga: allow compile testing of Stratix 10 / Agilex clocks")
> 552418658acd ("clk: socfpga: use ARCH_INTEL_SOCFPGA also for 32-bit ARM SoCs (and compile test)")
>
Thanks Stephen. This is a result of compile testing and was already
fixed via clk tree. You should not have the warning after all the merges.
https://lore.kernel.org/lkml/20210314110709.32599-1-krzysztof.kozlowski@canonical.com/
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-06 6:34 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 0:45 linux-next: build warning after merge of the arm-soc tree Stephen Rothwell
2021-04-06 0:45 ` Stephen Rothwell
2021-04-06 6:34 ` Krzysztof Kozlowski [this message]
2021-04-06 6:34 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2024-07-02 7:49 Stephen Rothwell
2024-07-02 11:55 ` Marek Behún
2024-07-30 10:05 ` Stephen Rothwell
2023-06-22 0:48 Stephen Rothwell
2023-06-22 0:48 ` Stephen Rothwell
2023-06-22 8:19 ` Arnd Bergmann
2023-06-22 8:19 ` Arnd Bergmann
2023-06-22 8:26 ` Krzysztof Kozlowski
2023-06-22 8:26 ` Krzysztof Kozlowski
2023-06-22 13:55 ` Rob Herring
2023-06-22 13:55 ` Rob Herring
2021-12-22 21:59 Stephen Rothwell
2021-12-22 21:59 ` Stephen Rothwell
2021-12-22 23:22 ` Arnd Bergmann
2021-12-22 23:22 ` Arnd Bergmann
2021-12-22 23:58 ` Florian Fainelli
2021-12-22 23:58 ` Florian Fainelli
2021-12-23 8:50 ` Arınç ÜNAL
2021-12-23 8:50 ` Arınç ÜNAL
2021-12-23 18:18 ` Florian Fainelli
2021-12-23 18:18 ` Florian Fainelli
2021-10-25 23:39 Stephen Rothwell
2021-10-25 23:39 ` Stephen Rothwell
2021-10-26 6:15 ` Joel Stanley
2021-10-26 6:15 ` Joel Stanley
2022-01-20 3:22 ` Stephen Rothwell
2022-01-20 3:22 ` Stephen Rothwell
2022-01-20 6:03 ` ChiaWei Wang
2022-01-20 6:03 ` ChiaWei Wang
2019-08-15 23:25 Stephen Rothwell
2019-08-15 23:25 ` Stephen Rothwell
2019-08-15 23:23 Stephen Rothwell
2019-08-15 23:23 ` Stephen Rothwell
2019-04-29 23:28 Stephen Rothwell
2019-04-29 23:28 ` Stephen Rothwell
2019-05-03 6:49 ` Linus Walleij
2019-05-03 6:49 ` Linus Walleij
2019-05-03 12:57 ` Arnd Bergmann
2019-05-03 12:57 ` Arnd Bergmann
2014-01-19 23:39 Stephen Rothwell
2014-01-19 23:39 ` Stephen Rothwell
2014-01-19 23:39 ` Stephen Rothwell
2012-03-19 7:39 Stephen Rothwell
2012-03-19 7:39 ` Stephen Rothwell
2012-03-19 7:39 ` Stephen Rothwell
2012-03-19 9:40 ` Arnd Bergmann
2012-03-19 9:40 ` Arnd Bergmann
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=190b8e95-2a96-142e-7b98-34318eea6804@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=arnd@arndb.de \
--cc=dinguyen@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.