From: <Conor.Dooley@microchip.com>
To: <vineetg@rivosinc.com>, <linux-riscv@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <palmer@rivosinc.com>,
<cmuellner@ventanamicro.com>, <linux@rivosinc.com>
Subject: Re: [PATCH v2] riscv: ztso: disallow elf binaries needing TSO
Date: Fri, 16 Sep 2022 16:37:00 +0000 [thread overview]
Message-ID: <d30b4730-b447-e8bf-fe1b-edaf35345b65@microchip.com> (raw)
In-Reply-To: <adf840d4-b5f1-4b1f-faac-d735465028e9@rivosinc.com>
On 16/09/2022 17:28, Vineet Gupta wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 9/15/22 23:58, Conor.Dooley@microchip.com wrote:
>> Also, since this is not marked as a fix, why would we not just apply the
>> patchset from Palmer that looks like a more complete version of this
>> patch:
>> https://lore.kernel.org/linux-riscv/20220902034352.8825-1-palmer@rivosinc.com/
>>
>> Maybe you could offer an R-b or some comments on that patch instead?
>
> Sure I didn't know about that patch and my idea was just to get the ball
> rolling so tooling at least can start having tso bits as last time
> around that was the blocker to getting stuff in binutils and gcc etc.
Ye nw, sure I completely forgot what the order was between frozen,
public review & ratification was ;)
prev parent reply other threads:[~2022-09-16 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 3:05 [PATCH] riscv: ztso: disallow elf binaries needing TSO Vineet Gupta
2022-09-16 4:23 ` [PATCH v2] " Vineet Gupta
2022-09-16 6:34 ` Conor.Dooley
[not found] ` <CAHYeh+okQuVQjRX_6CwEK5-zWFDcRfUF132WXt2BNbMSAP8_mA@mail.gmail.com>
2022-09-16 6:50 ` Conor.Dooley
2022-09-16 6:58 ` Conor.Dooley
2022-09-16 9:54 ` Palmer Dabbelt
2022-09-16 16:28 ` Vineet Gupta
2022-09-16 16:37 ` Conor.Dooley [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=d30b4730-b447-e8bf-fe1b-edaf35345b65@microchip.com \
--to=conor.dooley@microchip.com \
--cc=cmuellner@ventanamicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rivosinc.com \
--cc=palmer@rivosinc.com \
--cc=vineetg@rivosinc.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