[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240108-a56ba0dfd1779e4ab6893d16@orel>
Date: Mon, 8 Jan 2024 12:35:13 +0100
From: Andrew Jones <ajones@...tanamicro.com>
To: Andrea Parri <parri.andrea@...il.com>
Cc: Christoph Müllner <christoph.muellner@...ll.eu>,
Heiko Stuebner <heiko@...ech.de>, linux-riscv@...ts.infradead.org, palmer@...belt.com,
paul.walmsley@...ive.com, linux-kernel@...r.kernel.org, David.Laight@...lab.com,
Conor Dooley <conor@...nel.org>
Subject: Re: Re: [PATCH v3 0/2] Add Zawrs support and use it for spinlocks
On Fri, Oct 20, 2023 at 12:19:38PM +0200, Andrea Parri wrote:
> (Removing Heiko's @vrull address from Cc:, since it seemed to bounce, keeping
> his @sntech address.)
>
> > I had a quick look at your changes, and they look good to me.
>
> Great. Thank you for looking them over.
>
> > Did you agree with Palmer about testing requirements?
> > I.e., do we need to run this on hardware that implements Zawrs in a
> > non-trivial way?
>
> I didn't quite discuss such specific requirements or hardware implementations,
> but I agree that's a valid concern. Not that I currently have access to such
> hardware; any further inputs/data will be appreciated.
>
> > I can try to raise the priority on this here, but can't promise anything.
> > For me it is also ok if you take over this patchset.
>
> Thanks. Either way works for me. No urgency from my side. I'd say - let us
> leave this up to the community/other reviewers. (IIUC, Palmer was recovering
> from a certain flu and might need more time than usual to get back here.)
>
Hi everyone,
I'm also interested in seeing this series resurrected and making progress
again. I'd be happy to help out in any way. It's not clear to me if it has
a current owner. If not, then I could start shepherding the patches with
their authorships intact.
I may be able to do some testing on an FPGA too.
Thanks,
drew
Powered by blists - more mailing lists