From: Sai Prakash Ranjan <quic_saipraka@quicinc.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Marc Zyngier <maz@kernel.org>,
"Trilok Soni" <quic_tsoni@quicinc.com>,
<quic_psodagud@quicinc.com>, gregkh <gregkh@linuxfoundation.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCHv10 4/6] drm/meson: Fix overflow implicit truncation warnings
Date: Thu, 28 Apr 2022 08:33:15 +0530 [thread overview]
Message-ID: <65531cb4-efff-1e0e-2bac-7c7759ff55cd@quicinc.com> (raw)
In-Reply-To: <CAK8P3a3_Ea2Szn61D-t--52V-zk+B-sq2mi5YbfMbTim7M9ZAQ@mail.gmail.com>
On 4/27/2022 9:29 PM, Arnd Bergmann wrote:
> On Thu, Feb 24, 2022 at 7:07 AM Sai Prakash Ranjan
> <quic_saipraka@quicinc.com> wrote:
>> Fix -Woverflow warnings for drm/meson driver which is a result
>> of moving arm64 custom MMIO accessor macros to asm-generic function
>> implementations giving a bonus type-checking now and uncovering these
>> overflow warnings.
>>
>> drivers/gpu/drm/meson/meson_viu.c: In function ‘meson_viu_init’:
>> drivers/gpu/drm/meson/meson_registers.h:1826:48: error: large integer implicitly truncated to unsigned type [-Werror=overflow]
>> #define VIU_OSD_BLEND_REORDER(dest, src) ((src) << (dest * 4))
>> ^
>> drivers/gpu/drm/meson/meson_viu.c:472:18: note: in expansion of macro ‘VIU_OSD_BLEND_REORDER’
>> writel_relaxed(VIU_OSD_BLEND_REORDER(0, 1) |
>> ^~~~~~~~~~~~~~~~~~~~~
>>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>> Cc: Neil Armstrong <narmstrong@baylibre.com>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Signed-off-by: Sai Prakash Ranjan <quic_saipraka@quicinc.com>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
>
> It took me a bit to understand why we got the warning in the first place, but I
> should have just read the patch description, it's all there....
Right :)
Thanks,
Sai
next prev parent reply other threads:[~2022-04-28 3:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 6:07 [PATCHv10 0/6] lib/rwmmio/arm64: Add support to trace register reads/writes Sai Prakash Ranjan
2022-02-24 6:07 ` [PATCHv10 1/6] arm64: io: Use asm-generic high level MMIO accessors Sai Prakash Ranjan
2022-04-27 15:51 ` Arnd Bergmann
2022-02-24 6:07 ` [PATCHv10 2/6] coresight: etm4x: Use asm-generic IO memory barriers Sai Prakash Ranjan
2022-04-27 15:53 ` Arnd Bergmann
2022-02-24 6:07 ` [PATCHv10 3/6] irqchip/tegra: Fix overflow implicit truncation warnings Sai Prakash Ranjan
2022-02-24 6:07 ` [PATCHv10 4/6] drm/meson: " Sai Prakash Ranjan
2022-04-27 15:59 ` Arnd Bergmann
2022-04-28 3:03 ` Sai Prakash Ranjan [this message]
2022-02-24 6:07 ` [PATCHv10 5/6] lib: Add register read/write tracing support Sai Prakash Ranjan
2022-02-24 13:57 ` Steven Rostedt
2022-02-25 3:55 ` Sai Prakash Ranjan
2022-04-27 16:14 ` Arnd Bergmann
2022-04-28 3:16 ` Sai Prakash Ranjan
2022-02-24 6:07 ` [PATCHv10 6/6] asm-generic/io: Add logging support for MMIO accessors Sai Prakash Ranjan
2022-04-08 11:17 ` [PATCHv10 0/6] lib/rwmmio/arm64: Add support to trace register reads/writes Sai Prakash Ranjan
2022-04-21 2:00 ` Sai Prakash Ranjan
2022-04-27 15:50 ` Arnd Bergmann
2022-04-28 3:02 ` Sai Prakash Ranjan
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=65531cb4-efff-1e0e-2bac-7c7759ff55cd@quicinc.com \
--to=quic_saipraka@quicinc.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maz@kernel.org \
--cc=narmstrong@baylibre.com \
--cc=quic_psodagud@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=will@kernel.org \
/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