From: Paul Walmsley <paul.walmsley@sifive.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: krste@berkeley.edu, aou@eecs.berkeley.edu,
waterman@eecs.berkeley.edu, Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
palmer@dabbelt.com, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] Documentation: riscv: add patch acceptance guidelines
Date: Sun, 24 Nov 2019 18:48:54 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1911241841210.22625@viisi.sifive.com> (raw)
In-Reply-To: <CAPcyv4iqTR8s0v8jH7haWCBQAzhZinUEsypiH7Ts9FCf+F9Bvg@mail.gmail.com>
On Sat, 23 Nov 2019, Dan Williams wrote:
> I'm open to updating the headers to make a section heading that
> matches what you're trying to convey, however that header definition
> should be globally agreed upon. I don't want the document that tries
> to clarify per-subsystem behaviours itself to have per-subsystem
> permutations. I think we, subsystem maintainers, at least need to be
> able to agree on the topics we disagree on.
Unless you're planning to, say, follow up with some kind of automated
process working across all of the profile documents in such a way that it
would make technical sense for the different sections to be standardized,
I personally don't see any need at all for profile document
standardization. As far as I can tell, these documents are meant for
humans, rather than computers, to read. And in the absence of a strong
technical rationale to limit how maintainers express themselves here, I
don't think it's justified.
- 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-25 2:49 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
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 [this message]
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.1911241841210.22625@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).