[PATCH v2 2/2] arch/riscv: Add bitrev.h file to support rev8 and brev8

Yury Norov ynorov at nvidia.com
Fri Apr 17 12:27:57 PDT 2026


On Thu, Apr 16, 2026 at 08:29:17PM -0700, Nathan Chancellor wrote:
> 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.

OK, roger. The material is removed already.



More information about the linux-riscv mailing list