From: Sasha Levin <sashal@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
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
Subject: Re: [PATCH] docs: remove Assisted-by references
Date: Fri, 9 Oct 2026 06:09:02 -0400 [thread overview]
Message-ID: <asi9PhPrAv0StYEi@laps> (raw)
In-Reply-To: <20261009093835.GA680229@killaraus.ideasonboard.com>
On Fri, Oct 09, 2026 at 11:38:35AM +0200, Laurent Pinchart wrote:
>Hi Sasha,
>
>On Fri, Oct 09, 2026 at 04:31:37AM -0400, Sasha Levin wrote:
>> The Maintainers Summit reached consensus to deprecate the Assisted-by
>> tag. Remove the documentation requiring it.
>
>Please explain the rationale in the commit message. I'm sure you know
>how sensitive this topic is for many people, the more opaque changes are
>the more questions and frustration they will generate.
Ack, sorry. Let me withdraw this patch until the LWN coverage is up too.
For context, this wasn't even on the schedule: I believe it was Jon who asked
if anyone still find it useful, no one really voiced a strong opinion in favor,
so we suggested that we should just send a patch.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-09 10:09 UTC|newest]
Thread overview: 45+ 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 [this message]
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 15:02 ` Lorenzo Stoakes (ARM)
2026-10-13 16:58 ` Kees Cook
2026-10-13 17:32 ` Laurent Pinchart
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
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=asi9PhPrAv0StYEi@laps \
--to=sashal@kernel.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=joe@perches.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox