From: Matthew Wilcox <willy@infradead.org>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: krste@berkeley.edu, aou@eecs.berkeley.edu,
waterman@eecs.berkeley.edu, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
palmer@dabbelt.com, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] Documentation: riscv: add patch acceptance guidelines
Date: Fri, 22 Nov 2019 19:58:27 -0800 [thread overview]
Message-ID: <20191123035827.GZ20752@bombadil.infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1911221842200.14532@viisi.sifive.com>
On Fri, Nov 22, 2019 at 06:44:39PM -0800, Paul Walmsley wrote:
> Documentation/riscv/patch-acceptance.rst | 32 ++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/riscv/patch-acceptance.rst
Should this be linked into the toctree somewhere so it's findable
on kernel.org? Maybe add a line to Documentation/process/index.rst
to include ../riscv/patch-acceptance.rst?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-11-23 3:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 2:44 [PATCH] Documentation: riscv: add patch acceptance guidelines Paul Walmsley
2019-11-23 3:58 ` Matthew Wilcox [this message]
2019-11-23 23:38 ` Paul Walmsley
2019-11-23 16:39 ` Jonathan Corbet
2019-11-23 23:27 ` Paul Walmsley
2019-11-23 23:35 ` Dan Williams
2019-11-23 23:49 ` Paul Walmsley
2019-11-24 0:01 ` Dan Williams
2019-11-24 0:42 ` Paul Walmsley
2019-11-24 3:38 ` Dan Williams
2019-11-25 2:48 ` Paul Walmsley
2019-11-25 3:20 ` Dan Williams
2019-11-25 15:57 ` Jonathan Corbet
2019-11-23 18:29 ` Palmer Dabbelt
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=20191123035827.GZ20752@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=krste@berkeley.edu \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=waterman@eecs.berkeley.edu \
/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).