On Thu, 2026-10-15 at 19:48 +0200, Philippe Mathieu-Daudé wrote:
> On 15/10/26 19:42, Pierrick Bouvier wrote:
> > On 10/15/2026 10:37 AM, Philippe Mathieu-Daudé wrote:
> > > On 14/10/26 23:05, Pierrick Bouvier wrote:
> > > > Signed-off-by: Pierrick Bouvier
> > > > <[email protected]>
> > > > ---
> > > >    target/riscv/cpu.h | 2 +-
> > > >    1 file changed, 1 insertion(+), 1 deletion(-)
> > > > 
> > > > diff --git a/target/riscv/cpu.h b/target/riscv/cpu.h
> > > > index 8c8ffe94cd8..00650a66dcb 100644
> > > > --- a/target/riscv/cpu.h
> > > > +++ b/target/riscv/cpu.h
> > > > @@ -755,7 +755,7 @@ FIELD(EXT_TB_FLAGS, BIG_ENDIAN, 33, 1)
> > > >    #ifdef TARGET_RISCV32
> > > >    #define riscv_cpu_mxl(env)  ((void)(env), MXL_RV32)
> > > >    #else
> > > > -static inline RISCVMXL riscv_cpu_mxl(CPURISCVState *env)
> > > > +static inline RISCVMXL riscv_cpu_mxl(const CPURISCVState *env)
> > > >    {
> > > >        return env->misa_mxl;
> > > >    }
> > > 
> > > Reviewed 6 weeks ago and in Alistair riscv-next queue IIRC:
> > > https://lore.kernel.org/qemu-devel/20260901095229.72018-17-
> > > [email protected]/
> > > 
> > > Anyway,
> > > Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
> > > 
> > 
> > Did you flush the rest, or is it going through all submaintainers
> > trees?
> > 
> > I feel that system wide series like this should be sent on their
> > own at
> > once to avoid having a state spread across multiple people with
> > different latencies.
> 
> No, Alistair queued patches I'm depending on, and I consider a
> maintainer sending the "patch queued" message a lock on the
> patch. I'm stuck waiting for preliminary riscv-related patches
> to get merge to reduce conflict with Alistair tree. Meanwhile
> my tree grows so I'm not sure anymore it is a good process,
> maybe I should have posted a PR and let Alistair deal with
> the rebase conflicts. We still have 10 days until the freeze
> so I guess we are still in time.

Sorry, with all the conference travel the last month I haven't had a
chance to get through patches and send PRs, so it's been a bit delayed.
Then there was a conflict with the meson tests in the first PR. An
updated PR should be sent today and hopefully merged soon

Alistair

Reply via email to