From: Palmer Dabbelt <palmer@rivosinc.com>
To: Conor Dooley <conor@kernel.org>, Atish Patra <atishp@rivosinc.com>
Cc: corbet@lwn.net, Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
aou@eecs.berkeley.edu, conor.dooley@microchip.com,
Atish Patra <atishp@rivosinc.com>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@rivosinc.com
Subject: [PATCH v2 0/4] Documentation: RISC-V: patch-acceptance changes
Date: Wed, 12 Oct 2022 21:56:15 -0700 [thread overview]
Message-ID: <20221013045619.18906-1-palmer@rivosinc.com> (raw)
We talked about this during Plumbers and it seems like there was pretty
minor feedback on the v1. I don't intend on committing this for the
current merge window, as it's only been through one round of review and
I don't see any reason to rush it. Like last time we're just violating
this as the status quo, so we can stick with that as we sort out the
wording.
Changes since v1 <https://lore.kernel.org/all/Yyn9FJ4iuzJTfO1T@spud/t/#mcc9b5e547a2ca2b25d7f78a4d2572f39ddc5593e>:
* Various minor wording changes.
* "UEFI forum specifications" instead of just "UEFI specifications".
* New patch 4 with implementor -> implementer
* Atish and Conor's Reviewed-by.
next reply other threads:[~2022-10-13 4:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 4:56 Palmer Dabbelt [this message]
2022-10-13 4:56 ` [PATCH 1/4] Documentation: RISC-V: Fix a typo in patch-acceptance Palmer Dabbelt
2022-10-13 5:08 ` Anup Patel
2022-10-13 4:56 ` [PATCH 2/4] Documentation: RISC-V: Allow patches for non-standard behavior Palmer Dabbelt
2022-10-13 5:09 ` Anup Patel
2022-11-18 10:49 ` Paul Walmsley
2022-11-24 22:20 ` Conor Dooley
2022-10-13 4:56 ` [PATCH 3/4] Documentation: RISC-V: Mention the UEFI Standards Palmer Dabbelt
2022-10-13 5:10 ` Anup Patel
2022-10-13 4:56 ` [PATCH 4/4] Documentation: RISC-V: patch-acceptance: s/implementor/implementer Palmer Dabbelt
2022-10-13 5:11 ` Anup Patel
2022-10-13 11:39 ` 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=20221013045619.18906-1-palmer@rivosinc.com \
--to=palmer@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rivosinc.com \
--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: 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
all inboxes | Powered by JetHome®