From: Paul Walmsley <paul.walmsley@sifive.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, krste@berkeley.edu,
waterman@eecs.berkeley.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] Documentation: riscv: add patch acceptance guidelines
Date: Sat, 23 Nov 2019 15:49:56 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1911231546450.14532@viisi.sifive.com> (raw)
In-Reply-To: <CAPcyv4hmagCVLCTYmmv0U8-YD5BEoQPV=wtm5hbp3MxqwZRQUA@mail.gmail.com>
On Sat, 23 Nov 2019, Dan Williams wrote:
> On Sat, Nov 23, 2019 at 3:27 PM Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
> > 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.
>
> Those could likely be automated to highlight warnings that a given
> subsystem treats as errors, but wherever possible my expectation is
> that the policy should be specified globally.
>
> > Is that summary accurate, or did I miss some additional steps?
>
> I'll go fixup and get the into patch submitted today then we can go from
> there.
I guess I'm still looking for guidance along the lines of my earlier
question: what (if anything) would we need to change about the current
patch to have it work with the maintainer profile documentation (beyond
the "P:" entry in MAINTAINERS) ?
- Paul
next prev parent reply other threads:[~2019-11-23 23:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 2:44 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
2019-11-23 23:35 ` Dan Williams
2019-11-23 23:49 ` Paul Walmsley [this message]
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.1911231546450.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
all inboxes | Powered by JetHome®