From: Dan Carpenter <error27@gmail.com>
To: Arnaldo Melo <arnaldo.melo@gmail.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Jiri Kosina <jikos@kernel.org>,
ksummit@lists.linux.dev, sashiko@lists.linux.dev
Subject: Re: Patch pre-submission to Sashiko
Date: Mon, 19 Oct 2026 10:02:32 +0300 [thread overview]
Message-ID: <atXAiG_OL-TOKhJT@stanley.mountain> (raw)
In-Reply-To: <49D0633D-3576-4F42-9934-85663D11EC15@gmail.com>
On Sat, Oct 17, 2026 at 03:38:36PM -0300, Arnaldo Melo wrote:
>
>
> On October 17, 2026 3:20:47 PM GMT-03:00, Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> >On Sat Oct 17, 2026 at 5:28 PM UTC, Jiri Kosina wrote:
> >>
> >> [ in the spirit of the concluding discussion at this year's maintainers
> >> summit, I'm using this list outside of actual maintainer summit
> >> planning :) ]
> >>
> >> I have just received a v1 to v11 patchset submission within roughly one
> >> day timeframe.
> >>
> >> Neither myself nor anyone else did comment with any review feedback,
> >> except for Sashiko. Which I believe is what triggered all the immediate
> >> resubmissions.
> >>
> >> I don't think this is sustanable.
> >
> >I think it's just fine. I encourage developers to keep the spam going.
>
> Yay, agreed, it's not like before AI people were reading all of lkml
I read everything that's sent to drivers/staging. I've read it in the
order that it arrives and I've done that since 2010... But these days
people are treating the list like a pre-submit AI checker which sucks.
I feel like people are saying we should just accept that mailing lists
are just AI checker interfaces instead of being intended for humans...
I think adding a 24 hour delay to the AI review solves this. It seems
to be working for networking. It will likely push people to use AI
locally which is even better.
> (or other voluminous lists) traffic, just ignore what clearly is a
> conversation that now happens way faster than in the past until you
> see it calmed down
>
> The problem was not getting feedback at all, now people complain that
> feedback is being provided timely and then that people are responding
> to feedback in a timely fashion?
That has never been a problem on drivers/staging. Greg responds
to every email and when he was on vacation then I responded to
every email.
regards,
dan carpenter
next prev parent reply other threads:[~2026-10-19 7:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 17:28 Patch pre-submission to Sashiko Jiri Kosina
2026-10-17 18:02 ` Theodore Tso
2026-10-19 11:02 ` johannes.goede
2026-10-19 20:27 ` Theodore Tso
2026-10-20 14:20 ` Bart Van Assche
2026-10-20 19:21 ` Theodore Tso
2026-10-20 20:15 ` Miguel Ojeda
2026-10-20 20:43 ` Shuah Khan
2026-10-17 18:20 ` Alexei Starovoitov
2026-10-17 18:38 ` Arnaldo Melo
2026-10-19 7:02 ` Dan Carpenter [this message]
2026-10-18 11:46 ` Mark Brown
2026-10-17 18:20 ` Linus Torvalds
2026-10-17 20:10 ` Roman Gushchin
2026-10-18 13:41 ` Steven Rostedt
2026-10-18 18:41 ` Kees Cook
2026-10-18 18:58 ` Linus Torvalds
2026-10-19 5:55 ` Oliver Slapinski
2026-10-17 19:42 ` Andrew Lunn
2026-10-18 11:54 ` Mark Brown
2026-10-18 16:48 ` Laurent Pinchart
2026-10-19 6:25 ` Krzysztof Kozlowski
2026-10-19 7:26 ` David Woodhouse
2026-10-19 11:40 ` Michal Simek
2026-10-19 12:02 ` Julia Lawall
2026-10-19 12:46 ` Michal Simek
2026-10-19 12:57 ` Julia Lawall
2026-10-19 17:30 ` Rodrigo Vivi
2026-10-19 17:53 ` Shuah Khan
2026-10-19 18:17 ` Arnaldo Melo
2026-10-19 20:35 ` Theodore Tso
2026-10-20 2:28 ` Chen-Yu Tsai
2026-10-20 8:36 ` Jiri Kosina
2026-10-20 8:48 ` Vlastimil Babka (SUSE)
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=atXAiG_OL-TOKhJT@stanley.mountain \
--to=error27@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=jikos@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=sashiko@lists.linux.dev \
/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