From: Philip Li <philip.li@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
Dmitry Baryshkov <lumag@kernel.org>, <llvm@lists.linux.dev>,
<oe-kbuild-all@lists.linux.dev>,
Stephen Boyd <swboyd@chromium.org>
Subject: Re: [linux-next:master 3022/4739] drivers/gpu/drm/msm/msm.o: warning: objtool: msm_dp_ctrl_on_stream(): unexpected end of section .text.msm_dp_ctrl_on_stream
Date: Thu, 3 Jul 2025 09:38:37 +0800 [thread overview]
Message-ID: <aGXfHf7dwomigqi1@rli9-mobl> (raw)
In-Reply-To: <20250702214459.GC2103156@ax162>
On Wed, Jul 02, 2025 at 02:44:59PM -0700, Nathan Chancellor wrote:
> + Dmitry's @kernel.org address, should these reports use .mailmap from
> mainline to ensure they get sent to up to date addresses?
Thanks Nathan, I will update the bot to use the correct address from the latest
.mailmap.
>
> On Wed, Jul 02, 2025 at 02:37:16PM -0700, Nathan Chancellor wrote:
> > On Wed, Jun 25, 2025 at 10:16:55AM +0800, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > > head: 2ae2aaafb21454f4781c30734959cf223ab486ef
> > > commit: 8583a655f2c2bb442e2a2668680f419aa4c511d1 [3022/4739] drm/msm/dp: move/inline ctrl register functions
> > > config: x86_64-buildonly-randconfig-005-20250625 (https://download.01.org/0day-ci/archive/20250625/202506251051.7rmus46j-lkp@intel.com/config)
> > > compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project 6146a88f60492b520a36f8f8f3231e15f3cc6082)
> > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250625/202506251051.7rmus46j-lkp@intel.com/reproduce)
> > >
> > > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > > the same patch/commit), kindly add following tags
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202506251051.7rmus46j-lkp@intel.com/
> > >
> > > All warnings (new ones prefixed by >>):
> > >
> > > >> drivers/gpu/drm/msm/msm.o: warning: objtool: msm_dp_ctrl_on_stream(): unexpected end of section .text.msm_dp_ctrl_on_stream
> >
> > This appears to be a case similar to [1] and [2], where clang has been
> > able to figure out that there will be a divide by zero in the else
> > branch of msm_dp_ctrl_config_msa(). Should pixel_div be adjusted to 1 or
> > should the divide by zero be avoided by returning early? I believe Bill
> > is still looking into trying to make this less distructive in LLVM but
> > it should still probably be fixed for LLVM 20, which is already
> > released.
> >
> > [1]: https://lore.kernel.org/CAHk-=wiq=E0fwJLFpCc3wPY_9BPZF3dbdqGgVoOmK9Ykj5JEeg@mail.gmail.com/
> > [2]: https://lore.kernel.org/20250609213505.GA1634981@ax162/
> >
> > Cheers,
> > Nathan
> >
>
prev parent reply other threads:[~2025-07-03 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 2:16 [linux-next:master 3022/4739] drivers/gpu/drm/msm/msm.o: warning: objtool: msm_dp_ctrl_on_stream(): unexpected end of section .text.msm_dp_ctrl_on_stream kernel test robot
2025-07-02 21:37 ` Nathan Chancellor
2025-07-02 21:44 ` Nathan Chancellor
2025-07-03 1:38 ` Philip Li [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=aGXfHf7dwomigqi1@rli9-mobl \
--to=philip.li@intel.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=lumag@kernel.org \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=swboyd@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