From: Philip Li <philip.li@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: "Christian Marangi (Ansuel)" <ansuelsmth@gmail.com>,
kernel test robot <lkp@intel.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Ulf Hansson <ulf.hansson@linaro.org>, <llvm@lists.linux.dev>,
<oe-kbuild-all@lists.linux.dev>
Subject: Re: [linux-next:master 9185/10024] drivers/pmdomain/mediatek/airoha-cpu-pmdomain.c:59:2: error: write to reserved register 'R7'
Date: Wed, 22 Jan 2025 09:33:40 +0800 [thread overview]
Message-ID: <Z5BK9DP87L/qGp2q@rli9-mobl> (raw)
In-Reply-To: <20250120180236.GA484463@ax162>
On Mon, Jan 20, 2025 at 11:02:36AM -0700, Nathan Chancellor wrote:
> On Mon, Jan 20, 2025 at 06:39:10PM +0100, Christian Marangi (Ansuel) wrote:
> > Il giorno lun 20 gen 2025 alle ore 18:28 Nathan Chancellor
> > <nathan@kernel.org> ha scritto:
> > >
> > > On Mon, Jan 20, 2025 at 03:52:09PM +0100, Christian Marangi (Ansuel) wrote:
> > > > If only these test report were easy to report instead of me having to build
> > > > the massive llvm-20 dev version...
> > > >
[...]
>
> > My main complain is that a lot of times, the repro step reference clang
> > version or also gcc version that are actually not present in the download
> > link making the repro step (and script) not usable.
Apologize for this, we will resolve this to avoid such issue.
> >
> > Now I can use and try the previous version but given some compilation
> > error happens only on the most recent build tools (due to additional
> > warning and check introduced) It might be hard to repro.
> >
> > My honest suggestion to make this even more accessible would be
> > to also provide beta release of the build tool. Or at least add some
> > comments in the repro file suggesting also to try with the previous
> > version.
>
> This sounds like good feedback for the LKP folks. I have my own wrapper
Thanks all for the input, let me add it to our TODO list, before that we
will enhance the repro comments as suggested when the version is failed
for download.
> and processes for reproducing these issues because I do it a lot so I am
> unaware of the potential jagged edges with the reproducers. They are
> usually pretty responsive to requests/reports of problems with their
> stuff in my experience.
>
> Cheers,
> Nathan
>
prev parent reply other threads:[~2025-01-22 1:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 10:32 [linux-next:master 9185/10024] drivers/pmdomain/mediatek/airoha-cpu-pmdomain.c:59:2: error: write to reserved register 'R7' kernel test robot
2025-01-20 10:36 ` Christian Marangi (Ansuel)
2025-01-20 13:01 ` Ulf Hansson
2025-01-20 13:34 ` Sudeep Holla
2025-01-20 13:37 ` Christian Marangi (Ansuel)
2025-01-20 13:44 ` Sudeep Holla
2025-01-20 14:52 ` Christian Marangi (Ansuel)
2025-01-20 15:05 ` Sudeep Holla
2025-01-20 15:20 ` Christian Marangi (Ansuel)
2025-01-20 15:28 ` Christian Marangi (Ansuel)
2025-01-20 15:31 ` Christian Marangi (Ansuel)
2025-01-20 15:33 ` Sudeep Holla
2025-01-20 15:35 ` Sudeep Holla
2025-01-20 17:28 ` Nathan Chancellor
2025-01-20 17:39 ` Christian Marangi (Ansuel)
2025-01-20 18:02 ` Nathan Chancellor
2025-01-22 1:33 ` 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=Z5BK9DP87L/qGp2q@rli9-mobl \
--to=philip.li@intel.com \
--cc=ansuelsmth@gmail.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.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