From: Paul Walmsley <paul.walmsley@sifive.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: krste@berkeley.edu, aou@eecs.berkeley.edu,
waterman@eecs.berkeley.edu, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, palmer@dabbelt.com,
linux-riscv@lists.infradead.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] Documentation: riscv: add patch acceptance guidelines
Date: Sat, 23 Nov 2019 15:27:19 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1911231523390.14532@viisi.sifive.com> (raw)
In-Reply-To: <20191123092552.1438bc95@lwn.net>
Hi Jon,
On Sat, 23 Nov 2019, Jonathan Corbet wrote:
> On Fri, 22 Nov 2019 18:44:39 -0800 (PST) Paul Walmsley
> <paul.walmsley@sifive.com> wrote:
>
> > Formalize, in kernel documentation, the patch acceptance policy for
> > arch/riscv. In summary, it states that as maintainers, we plan to only
> > accept patches for new modules or extensions that have been frozen or
> > ratified by the RISC-V Foundation.
> >
> > We've been following these guidelines for the past few months. In the
> > meantime, we've received quite a bit of feedback that it would be
> > helpful to have these guidelines formally documented.
>
> If at all possible, I would really love to have this be part of the
> maintainer profile documentation:
>
> https://lwn.net/ml/linux-kernel/156821692280.2951081.18036584954940423225.stgit@dwillia2-desk3.amr.corp.intel.com/
>
> ...if we could only (hint...CC'd...) get Dan to resubmit it with the
> needed tweaks so it could be merged...
It looks like the main thing that would be needed would be to add the P:
entry with the path to our patch-acceptance.rst file into the MAINTAINERS
file, after Dan's patches are merged.
Of course, we could also add more information about sparse cleanliness,
checkpatch warnings, etc., but we mostly try to follow the common kernel
guidelines there.
Is that summary accurate, or did I miss some additional steps?
- Paul
_______________________________________________
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 23:27 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
2019-11-23 23:38 ` Paul Walmsley
2019-11-23 16:39 ` Jonathan Corbet
2019-11-23 23:27 ` Paul Walmsley [this message]
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=alpine.DEB.2.21.9999.1911231523390.14532@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--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=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).