From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <seanpaul@chromium.org>
Cc: Jonathan Marek <jonathan@marek.ca>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the drm-msm tree
Date: Thu, 17 Sep 2020 17:58:00 +1000 [thread overview]
Message-ID: <20200917175800.7a55e4fb@canb.auug.org.au> (raw)
In-Reply-To: <20200914121022.2c5c494a@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Hi all,
On Mon, 14 Sep 2020 12:10:22 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the drm-msm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpu/drm/msm/dsi/pll/dsi_pll_7nm.c: In function 'msm_dsi_pll_7nm_init':
> drivers/gpu/drm/msm/dsi/pll/dsi_pll_7nm.c:882:19: warning: conversion from 'long long unsigned int' to 'long unsigned int' changes value from '5000000000' to '705032704' [-Woverflow]
> 882 | pll->max_rate = 5000000000UL;
> | ^~~~~~~~~~~~
>
> Introduced by commit
>
> 1ef7c99d145c ("drm/msm/dsi: add support for 7nm DSI PHY/PLL")
I am still getting this warning.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-17 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 2:10 linux-next: build warning after merge of the drm-msm tree Stephen Rothwell
2020-09-17 7:58 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-21 3:16 Stephen Rothwell
2017-11-01 3:46 Stephen Rothwell
2017-11-01 15:19 ` Rob Clark
2017-08-03 3:12 Stephen Rothwell
2017-08-03 3:09 Stephen Rothwell
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=20200917175800.7a55e4fb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jonathan@marek.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.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;
as well as URLs for NNTP newsgroup(s).