From: "Björn Töpel" <bjorn@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>, palmer@dabbelt.com
Cc: conor@kernel.org, conor.dooley@microchip.com,
Paul Walmsley <paul.walmsley@sifive.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-riscv@lists.infradead.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: RISC-V: patch-acceptance: mention patchwork's role
Date: Tue, 13 Jun 2023 15:00:37 +0200 [thread overview]
Message-ID: <87mt13ldoq.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20230606-rehab-monsoon-12c17bbe08e3@wendy>
Conor Dooley <conor.dooley@microchip.com> writes:
> Palmer suggested at some point, not sure if it was in one of the
> weekly linux-riscv syncs, or a conversation at FOSDEM, that we
> should document the role of the automation running on our patchwork
> instance plays in patch acceptance.
>
> Add a short note to the patch-acceptance document to that end.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> I was also not sure if this was the correct doc for this, or whether a
> process/maintainer-riscv.rst file was better suited. There's clearly no
> rush on this though so ¯\_(ツ)_/¯
I'm fine with this file. Thanks for adding it!
Reviewed-by: Björn Töpel <bjorn@rivosinc.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-13 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 6:59 [PATCH v2] Documentation: RISC-V: patch-acceptance: mention patchwork's role Conor Dooley
2023-06-13 13:00 ` Björn Töpel [this message]
2023-06-15 17:14 ` Palmer Dabbelt
2023-06-15 17:20 ` 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=87mt13ldoq.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).