From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH] RISC-V: Provide a more helpful error message on invalid ISA strings
Date: Thu, 6 Jul 2023 18:46:25 +0100 [thread overview]
Message-ID: <20230706-acutely-undusted-940bf8afcdc2@spud> (raw)
In-Reply-To: <mhng-62c3565c-43f5-4a17-940a-e02483b19c33@palmer-ri-x1c9a>
[-- Attachment #1.1: Type: text/plain, Size: 740 bytes --]
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...)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-07-06 17:46 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 [this message]
2023-07-06 17:54 ` Palmer Dabbelt
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=20230706-acutely-undusted-940bf8afcdc2@spud \
--to=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@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