From: Andrea Parri <parri.andrea@gmail.com> To: "Christoph Müllner" <christoph.muellner@vrull.eu> Cc: Heiko Stuebner <heiko@sntech.de>, linux-riscv@lists.infradead.org, palmer@dabbelt.com, paul.walmsley@sifive.com, linux-kernel@vger.kernel.org, David.Laight@aculab.com, Andrew Jones <ajones@ventanamicro.com>, Conor Dooley <conor@kernel.org> Subject: Re: [PATCH v3 0/2] Add Zawrs support and use it for spinlocks Date: Fri, 20 Oct 2023 12:19:38 +0200 [thread overview] Message-ID: <ZTJUOji+B+dDbMKh@andrea> (raw) In-Reply-To: <CAEg0e7jkTOn1pjO=+GaiCZJ9_Yd2NcB1GMG=Q6m3-r0+Q0OjGQ@mail.gmail.com> (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.) Andrea
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Parri <parri.andrea@gmail.com> To: "Christoph Müllner" <christoph.muellner@vrull.eu> Cc: Heiko Stuebner <heiko@sntech.de>, linux-riscv@lists.infradead.org, palmer@dabbelt.com, paul.walmsley@sifive.com, linux-kernel@vger.kernel.org, David.Laight@aculab.com, Andrew Jones <ajones@ventanamicro.com>, Conor Dooley <conor@kernel.org> Subject: Re: [PATCH v3 0/2] Add Zawrs support and use it for spinlocks Date: Fri, 20 Oct 2023 12:19:38 +0200 [thread overview] Message-ID: <ZTJUOji+B+dDbMKh@andrea> (raw) In-Reply-To: <CAEg0e7jkTOn1pjO=+GaiCZJ9_Yd2NcB1GMG=Q6m3-r0+Q0OjGQ@mail.gmail.com> (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.) Andrea _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-10-20 10:19 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-21 11:47 [PATCH v3 0/2] Add Zawrs support and use it for spinlocks Heiko Stuebner 2023-05-21 11:47 ` Heiko Stuebner 2023-05-21 11:47 ` [PATCH v3 1/2] riscv: don't include kernel.h into alternative.h Heiko Stuebner 2023-05-21 11:47 ` Heiko Stuebner 2023-05-24 14:01 ` Andrew Jones 2023-05-24 14:01 ` Andrew Jones 2023-05-21 11:47 ` [PATCH v3 2/2] riscv: Add Zawrs support for spinlocks Heiko Stuebner 2023-05-21 11:47 ` Heiko Stuebner 2023-05-22 17:43 ` Conor Dooley 2023-05-22 17:43 ` Conor Dooley 2023-05-24 17:05 ` Andrew Jones 2023-05-24 17:05 ` Andrew Jones 2023-05-24 23:00 ` Palmer Dabbelt 2023-05-24 23:00 ` Palmer Dabbelt 2023-05-30 18:45 ` Andrea Parri 2023-05-30 18:45 ` Andrea Parri 2023-10-19 14:21 ` [PATCH v3 0/2] Add Zawrs support and use it " Andrea Parri 2023-10-19 14:21 ` Andrea Parri 2023-10-19 16:22 ` Christoph Müllner 2023-10-19 16:22 ` Christoph Müllner 2023-10-20 10:19 ` Andrea Parri [this message] 2023-10-20 10:19 ` Andrea Parri 2024-01-08 11:35 ` Andrew Jones 2024-01-08 11:35 ` Andrew Jones 2024-01-08 13:38 ` Andrea Parri 2024-01-08 13:38 ` Andrea Parri 2024-01-08 14:00 ` Christoph Müllner 2024-01-08 14:00 ` Christoph Müllner 2024-01-08 14:10 ` Andrew Jones 2024-01-08 14:10 ` Andrew Jones 2024-03-05 23:31 ` Charlie Jenkins 2024-03-05 23:31 ` Charlie Jenkins
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=ZTJUOji+B+dDbMKh@andrea \ --to=parri.andrea@gmail.com \ --cc=David.Laight@aculab.com \ --cc=ajones@ventanamicro.com \ --cc=christoph.muellner@vrull.eu \ --cc=conor@kernel.org \ --cc=heiko@sntech.de \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.