From: Palmer Dabbelt <palmer@rivosinc.com>
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH] RISC-V: Provide a more helpful error message on invalid ISA strings
Date: Thu, 06 Jul 2023 10:54:01 -0700 (PDT) [thread overview]
Message-ID: <mhng-cdc3010a-7bfe-4d5b-befe-d89a0c2c19b3@palmer-ri-x1c9a> (raw)
In-Reply-To: <20230706-acutely-undusted-940bf8afcdc2@spud>
On Thu, 06 Jul 2023 10:46:25 PDT (-0700), Conor Dooley wrote:
> On Thu, Jul 06, 2023 at 10:28:21AM -0700, Palmer Dabbelt wrote:
>> On Thu, 29 Jun 2023 16:17:27 PDT (-0700), Conor Dooley wrote:
>> > On Thu, Jun 29, 2023 at 03:35:03PM -0700, Palmer Dabbelt wrote:
>
>> > If you are gonna apply this for v6.5:
>> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>> > Otherwise, can I take this in my series? I probably need to extend it a la:
>>
>> I forgot about it and it looks like Drew pointed out some small issue. Do
>> you want to just clean that up and pick it up with your series?
>
> Drew's issue was actually with the related error prints that I was
> adding, not with your patch. Your patch is still good on its own, but I
> am perfectly happy to put it in my series. (I already did...)
OK, works for me.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-07-06 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 22:35 [PATCH] RISC-V: Provide a more helpful error message on invalid ISA strings Palmer Dabbelt
2023-06-29 23:17 ` Conor Dooley
2023-06-30 8:06 ` Andrew Jones
2023-07-06 17:28 ` Palmer Dabbelt
2023-07-06 17:46 ` Conor Dooley
2023-07-06 17:54 ` Palmer Dabbelt [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=mhng-cdc3010a-7bfe-4d5b-befe-d89a0c2c19b3@palmer-ri-x1c9a \
--to=palmer@rivosinc.com \
--cc=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).