From: <dan.j.williams@intel.com>
To: Sasha Levin <sashal@kernel.org>, <dan.j.williams@intel.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
<linux-kernel@vger.kernel.org>, Shuah Khan <shuah@kernel.org>,
Kees Cook <kees@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miguel Ojeda <ojeda@kernel.org>,
"Luis Chamberlain" <mcgrof@kernel.org>,
SeongJae Park <sj@kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
Simon Glass <simon.glass@canonical.com>,
NeilBrown <neilb@ownmail.net>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Theodore Ts'o <tytso@mit.edu>, Jonathan Corbet <corbet@lwn.net>,
Vlastimil Babka <vbabka@suse.cz>, <workflows@vger.kernel.org>,
<ksummit@lists.linux.dev>
Subject: Re: [PATCH] [v5] Documentation: Provide guidelines for tool-generated content
Date: Tue, 13 Jan 2026 10:50:44 -0800 [thread overview]
Message-ID: <69669404e2bf_875d10028@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <aWaSQsl8h2wnBjzj@laps>
Sasha Levin wrote:
[..]
> With a rule like the above, 1700+ contributors would have not been able to send
> their patch in.
Good point, I am not suggesting a Reviewed-by hurdle, but can see it
reading that way. I expect that there will always be a significant class
of contributions that will never need author trust to be accepted. Yes,
would need to be careful not to destroy that wellspring of new
contributors.
next prev parent reply other threads:[~2026-01-13 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 0:06 Dave Hansen
2026-01-13 5:30 ` Dan Carpenter
2026-01-13 9:28 ` Lorenzo Stoakes
2026-01-13 18:20 ` Dave Hansen
2026-01-13 18:20 ` dan.j.williams
2026-01-13 18:43 ` Sasha Levin
2026-01-13 18:50 ` dan.j.williams [this message]
2026-01-13 21:03 ` Alexei Starovoitov
2026-01-13 19:33 ` James Bottomley
2026-01-13 22:44 ` Steven Rostedt
2026-01-13 9:09 ` Lorenzo Stoakes
2026-01-13 10:36 ` Lee Jones
2026-01-13 18:05 ` Dave Hansen
2026-01-13 18:55 ` Geert Uytterhoeven
2026-01-15 15:04 ` Lee Jones
2026-01-13 19:22 ` Jonathan Corbet
2026-01-19 19:57 ` Dave Hansen
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=69669404e2bf_875d10028@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=corbet@lwn.net \
--cc=dan.carpenter@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mcgrof@kernel.org \
--cc=neilb@ownmail.net \
--cc=ojeda@kernel.org \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=simon.glass@canonical.com \
--cc=sj@kernel.org \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=workflows@vger.kernel.org \
/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