From: patchwork-bot+linux-riscv@kernel.org
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
conor@kernel.org, anup@brainfault.org
Subject: Re: [PATCH v3 0/4] Documentation: RISC-V: patch-acceptance changes
Date: Tue, 13 Dec 2022 17:40:17 +0000 [thread overview]
Message-ID: <167095321746.5951.711585297484375290.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221207020815.16214-1-palmer@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 6 Dec 2022 18:08:11 -0800 you wrote:
> This has a small textual change since the v2, but any change to the text
> is pretty important so I'm sending out a v3 rather than just silently
> squashing it in. Folks seemed generally OK with it, so unless there's
> any other feedback I'll target this for the merge window.
>
> Changes since v2 <https://lore.kernel.org/all/20221013045619.18906-1-palmer@rivosinc.com/>:
> * Remove the published timeline wording, to match the standard Linux
> policies.
>
> [...]
Here is the summary with links:
- [v3,1/4] Documentation: RISC-V: Fix a typo in patch-acceptance
https://git.kernel.org/riscv/c/37f0ab147799
- [v3,2/4] Documentation: RISC-V: Allow patches for non-standard behavior
(no matching commit)
- [v3,3/4] Documentation: RISC-V: Mention the UEFI Standards
https://git.kernel.org/riscv/c/68eabc72023f
- [v3,4/4] Documentation: RISC-V: patch-acceptance: s/implementor/implementer
https://git.kernel.org/riscv/c/a39c636506cb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-12-13 17:40 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
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 [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=167095321746.5951.711585297484375290.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--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