From: Jonathan Corbet <corbet@lwn.net>
To: Palmer Dabbelt <palmer@dabbelt.com>,
Conor Dooley <conor.dooley@microchip.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: riscv: note that counter access is part of the uABI
Date: Sat, 03 Dec 2022 03:45:35 -0700 [thread overview]
Message-ID: <87y1rooje8.fsf@meer.lwn.net> (raw)
In-Reply-To: <87359wpy9y.fsf@meer.lwn.net>
Jonathan Corbet <corbet@lwn.net> writes:
> Palmer Dabbelt <palmer@dabbelt.com> writes:
>> Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
>> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>>
>> I think I merged the last one of these, but if the doc folks pick it up
>> that's fine with me. Otherwise I'll take it when it comes back around,
>> so folks have time to take a look.
>
> "Doc folks" applied it, thanks. :)
Actually, I take that back. I'd missed this part from the patch:
> Based on an, as yet, unsent v2 of my other uABI changes. I don't expect
> it to be applicable, just getting a patch into patchwork while I don't
> forget about this.
...but b4 happily picked up a couple of *other* patches from this thread
and applied them instead; I've now undone that. Sorry for the noise.
jon
next prev parent reply other threads:[~2022-12-03 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y4XvnHIPw8ZuBZEk@wendy>
2022-12-01 13:51 ` [PATCH] Documentation: riscv: note that counter access is part of the uABI Conor Dooley
2022-12-01 19:21 ` Palmer Dabbelt
2022-12-03 10:38 ` Jonathan Corbet
2022-12-03 10:45 ` Jonathan Corbet [this message]
2022-12-03 10:56 ` Conor Dooley
2023-01-09 21:36 ` Atish Patra
2023-01-09 21:46 ` Conor Dooley
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=87y1rooje8.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=conor.dooley@microchip.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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;
as well as URLs for NNTP newsgroup(s).