From: "Heiko Stübner" <heiko@sntech.de>
To: linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Conor Dooley <conor@kernel.org>,
anup@brainfault.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>,
Anup Patel <anup@brainfault.org>,
Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: [PATCH v3 1/4] Documentation: RISC-V: Fix a typo in patch-acceptance
Date: Wed, 07 Dec 2022 16:42:17 +0100 [thread overview]
Message-ID: <1864243.TLkxdtWsSY@diego> (raw)
In-Reply-To: <20221207020815.16214-2-palmer@rivosinc.com>
Am Mittwoch, 7. Dezember 2022, 03:08:12 CET schrieb Palmer Dabbelt:
> I just stumbled on this when modifying the docs.
>
> Reviewed-by: Anup Patel <anup@brainfault.org>
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Reviewed-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-12-07 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 2:08 [PATCH v3 0/4] Documentation: RISC-V: patch-acceptance changes Palmer Dabbelt
2022-12-07 2:08 ` [PATCH v3 1/4] Documentation: RISC-V: Fix a typo in patch-acceptance Palmer Dabbelt
2022-12-07 15:42 ` Heiko Stübner [this message]
2022-12-07 2:08 ` [PATCH v3 2/4] Documentation: RISC-V: Allow patches for non-standard behavior Palmer Dabbelt
2022-12-07 15:41 ` Heiko Stübner
2022-12-13 17:39 ` Palmer Dabbelt
2022-12-07 2:08 ` [PATCH v3 3/4] Documentation: RISC-V: Mention the UEFI Standards Palmer Dabbelt
2022-12-07 15:44 ` Heiko Stübner
2022-12-07 2:08 ` [PATCH v3 4/4] Documentation: RISC-V: patch-acceptance: s/implementor/implementer Palmer Dabbelt
2022-12-07 15:44 ` Heiko Stübner
2022-12-13 17:39 ` [PATCH v3 0/4] Documentation: RISC-V: patch-acceptance changes Palmer Dabbelt
2022-12-13 17:40 ` patchwork-bot+linux-riscv
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=1864243.TLkxdtWsSY@diego \
--to=heiko@sntech.de \
--cc=anup@brainfault.org \
--cc=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.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