From: Nathan Chancellor <nathan@kernel.org>
To: Yury Norov <ynorov@nvidia.com>
Cc: Jinjie Ruan <ruanjinjie@huawei.com>,
yury.norov@gmail.com, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, linux@rasmusvillemoes.dk,
arnd@arndb.de, cp0613@linux.alibaba.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arch/riscv: Add bitrev.h file to support rev8 and brev8
Date: Thu, 16 Apr 2026 20:29:17 -0700 [thread overview]
Message-ID: <20260417032917.GA4041922@ax162> (raw)
In-Reply-To: <aeF5Q2XauRKBDssy@yury>
On Thu, Apr 16, 2026 at 08:34:28PM -0400, Yury Norov wrote:
> On Thu, Apr 16, 2026 at 04:14:41PM -0700, Nathan Chancellor wrote:
> > Yury, are you intending to send this series to Linus in the 7.1 merge
> > window?
>
> No, I'm already done with this merge window. This is the material for
> the next one, if ever.
>
> Just as said, I added this one for testing. I am so far have no feedback
> from robots. But your report is enough to drop it.
The lore.kernel.org link came from KernelCI but it does not look like
they do bisecting to identify the commit and notify the authors. It was
just sent to the linux-next mailing list.
> > If not, it shouldn't be in -next at this point.
>
> What for do we need -next, if not for early testing?
It is just for the two weeks of the merge window to ensure the tree
actually stabilizes. This is how it has always been.
https://lore.kernel.org/linux-next/aeDrt2FkMD6ZWaVS@sirena.org.uk/
https://lore.kernel.org/linux-next/ad9r3jEtJJNv0IiA@sirena.org.uk/
I think Mark meant to say 7.2 but still. Not trying to sound like a cop
or anything but the more problems there are in the tree, the harder it
is to triage new failures and perform additional testing.
Cheers,
Nathan
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-04-17 3:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 9:38 [PATCH v2 0/2] arch/riscv: Add bitrev.h file to support rev8 and brev8 Jinjie Ruan
2026-04-15 9:38 ` [PATCH v2 1/2] bitops: Define generic __bitrev8/16/32 for reuse Jinjie Ruan
2026-04-15 18:30 ` Yury Norov
2026-04-15 9:38 ` [PATCH v2 2/2] arch/riscv: Add bitrev.h file to support rev8 and brev8 Jinjie Ruan
2026-04-15 11:32 ` David Laight
2026-04-16 23:14 ` Nathan Chancellor
2026-04-17 0:34 ` Yury Norov
2026-04-17 3:29 ` Nathan Chancellor [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=20260417032917.GA4041922@ax162 \
--to=nathan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=cp0613@linux.alibaba.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rasmusvillemoes.dk \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=ynorov@nvidia.com \
--cc=yury.norov@gmail.com \
/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