[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4411deb-a06c-478f-9385-1701f4d9dbce@intel.com>
Date: Thu, 8 Jan 2026 11:16:19 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Sasha Levin <sashal@...nel.org>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Dave Hansen <dave@...1.net>, Dave Hansen <dave.hansen@...ux.intel.com>,
linux-kernel@...r.kernel.org, Shuah Khan <shuah@...nel.org>,
Kees Cook <kees@...nel.org>, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, Miguel Ojeda <ojeda@...nel.org>,
Luis Chamberlain <mcgrof@...nel.org>, SeongJae Park <sj@...nel.org>,
Dan Williams <dan.j.williams@...el.com>, Steven Rostedt
<rostedt@...dmis.org>, NeilBrown <neilb@...mail.net>,
Theodore Ts'o <tytso@....edu>, Jonathan Corbet <corbet@....net>,
Vlastimil Babka <vbabka@...e.cz>, workflows@...r.kernel.org,
ksummit@...ts.linux.dev
Subject: Re: [PATCH] [v3] Documentation: Provide guidelines for tool-generated
content
On 1/8/26 08:42, Sasha Levin wrote:
> I suppose that we can restate the same here, but whats the purpose?
> to put it in front of whatever media outlets might be looking?
Yeah, that's my only objection to adding the new hunk that James and
Lorenzo were suggesting. It's arguably covered earlier in _this_ document:
> +Guidelines
> +==========
....
> +tool-generated contributions. Ensure that you understand your entire
> +submission and are prepared to respond to review comments.
But, if folks feel it's that important a point, I guess mentioning it
twice-ish is OK.
Powered by blists - more mailing lists