From: Shuah Khan <skhan@linuxfoundation.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mark Brown <broonie@kernel.org>
Cc: Jori Koolstra <jkoolstra@xs4all.nl>, Kees Cook <kees@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Sasha Levin <sashal@kernel.org>,
corbet@lwn.net, federico.vaga@vaga.pv.it, apw@canonical.com,
joe@perches.com, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] docs: remove Assisted-by reference
Date: Tue, 13 Oct 2026 14:01:14 -0600 [thread overview]
Message-ID: <3c45e083-4e08-4699-adea-1d758baf8d0e@linuxfoundation.org> (raw)
In-Reply-To: <20261013170744.GA178151@killaraus.ideasonboard.com>
On 10/13/26 11:07, Laurent Pinchart wrote:
> On Tue, Oct 13, 2026 at 04:18:32PM +0100, Mark Brown wrote:
>> On Tue, Oct 13, 2026 at 02:55:59PM +0200, Laurent Pinchart wrote:
>>
>>> The absence of the tag on a suspicious series offered a low-effort way
>>> for maintainers to push back. What's the proposed low-effort replacement
>>> ?
>>
>> Greg's suggested asking "how did you test this?" or similar, a lot of
>> people just throwing stuff at the wall simply won't respond.
>
> I've done that too. I still find it better to have multiple tools at my
> disposal, I want to be able to tell people they're expected to disclose
> that the code they submit was generated.
Asking how the fix was found and tested has been helping me. I get silence
or didn't test it and that ends the discussion.
>
> Maybe Documentation/process/generated-content.rst is enough. As I wrote,
> what matters to me is the disclosure requirement, not the Assisted-by
> tag as such. I'm however concerned that it's even easier for
> contributors to ignore Documentation/process/generated-content.rst than
> the tag.
>
We could add documentation to call out the need for telling us why the patch
is necessary and how the code was verified in the commit message.
This will save time asking those questions.
thanks,
-- Shuah
prev parent reply other threads:[~2026-10-13 20:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 8:31 [PATCH] docs: remove Assisted-by references Sasha Levin
2026-10-09 9:38 ` Laurent Pinchart
2026-10-09 10:09 ` Sasha Levin
2026-10-09 10:05 ` Krzysztof Kozlowski
2026-10-09 10:24 ` Greg KH
2026-10-09 15:20 ` Jonathan Corbet
2026-10-11 1:04 ` Steven Rostedt
2026-10-12 15:42 ` Lorenzo Stoakes (ARM)
2026-10-13 11:19 ` Jori Koolstra
2026-10-13 12:38 ` Laurent Pinchart
2026-10-13 12:50 ` Jori Koolstra
2026-10-13 13:01 ` Laurent Pinchart
2026-10-13 13:24 ` Ricardo B. Marlière (SUSE)
2026-10-13 12:49 ` Lorenzo Stoakes (ARM)
2026-10-13 17:16 ` Laurent Pinchart
2026-10-13 12:31 ` Laurent Pinchart
2026-10-13 12:59 ` Lorenzo Stoakes (ARM)
2026-10-13 13:04 ` Krzysztof Kozlowski
2026-10-13 13:07 ` Lorenzo Stoakes (ARM)
2026-10-13 13:12 ` Laurent Pinchart
2026-10-13 13:29 ` Lorenzo Stoakes (ARM)
2026-10-13 13:37 ` Jori Koolstra
2026-10-13 14:52 ` Kees Cook
2026-10-13 14:54 ` Jori Koolstra
2026-10-13 14:58 ` Jori Koolstra
2026-10-13 17:12 ` Kees Cook
2026-10-13 17:42 ` Laurent Pinchart
2026-10-13 19:25 ` Kees Cook
2026-10-13 20:16 ` Laurent Pinchart
2026-10-13 20:45 ` Linus Torvalds
2026-10-13 15:02 ` Lorenzo Stoakes (ARM)
2026-10-13 16:58 ` Kees Cook
2026-10-13 17:32 ` Laurent Pinchart
2026-10-14 3:23 ` Theodore Tso
2026-10-13 4:24 ` Kees Cook
2026-10-13 5:56 ` Randy Dunlap
2026-10-13 6:18 ` Greg KH
2026-10-13 8:25 ` Kees Cook
2026-10-13 12:28 ` [PATCH] docs: remove Assisted-by reference Jori Koolstra
2026-10-13 12:55 ` Laurent Pinchart
2026-10-13 13:03 ` Jori Koolstra
2026-10-13 13:10 ` Laurent Pinchart
2026-10-13 13:20 ` Jori Koolstra
2026-10-13 13:55 ` Laurent Pinchart
2026-10-13 15:18 ` Mark Brown
2026-10-13 17:07 ` Laurent Pinchart
2026-10-13 20:01 ` Shuah Khan [this message]
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=3c45e083-4e08-4699-adea-1d758baf8d0e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=jkoolstra@xs4all.nl \
--cc=joe@perches.com \
--cc=kees@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.