From: "Stéphane Grosjean" <stephane.grosjean@free.fr>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: mailhol@kernel.org, Oliver Hartkopp <socketcan@hartkopp.net>,
linux-kernel@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: [PATCH 4/5] can: peak_usb: validate channel numbers in PCAN-USB FD
Date: Mon, 12 Oct 2026 16:08:47 +0200 (CEST) [thread overview]
Message-ID: <1228378911.1051074990.1791814127665.JavaMail.root@zimbra65-e11.priv.proxad.net> (raw)
In-Reply-To: <20261012-rare-pigeon-of-elegance-6014fe-mkl@pengutronix.de>
Thank you so much for your help, Marc. I really appreciate it.
Best regards,
-- Stéphane
----- Mail original -----
> On 12.10.2026 11:04:56, Stéphane Grosjean wrote:
> > I need help (or training) to figure out how to deal with these AI
> > bots:
> >
> > - How many of them are there before the changes are accepted? It
> > seems
> > that even if a patch has passed the Sashiko filter, we should
> > still
> > expect feedback from other bots...
>
> There's https://sashiko.dev/ , which replies within minutes (as long
> as
> you don't include the netdev mailing list).
>
> And there's https://netdev-ai.bots.linux.dev/, which embargoes the
> review for ~24h, but runs several LLMs with better models.
>
> > - The fact that there are multiple levels of bots isn’t a problem
> > in
> > itself, and is understandable. That feedback arrives on v1 even
> > though
> > v2 has already been analysed is also something I’m just learning:
> > so
> > when can we consider it safe to push a new version without fear
> > of
> > receiving comments on the previous one?
>
> Maybe you can mark the v1 as obsolete yourself with replying "pw-bot:
> cr".
> On a new line, without quotation marks, see:
>
> https://github.com/linux-netdev/nipa/blob/main/mailbot.rst
> https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#updating-patch-status
> https://github.com/linux-netdev/nipa/blob/e03d912ce66fd5d427cb9cf900409e1abc6eeba2/mailbot.py#L52-L81
>
> > - And finally, providing more explicit comments on our changes is
> > also
> > a good thing. But when those comments themselves become a source
> > of
> > problems and rejections—due to an overly nitpicky interpretation
> > by a
> > bot—it becomes far too time-consuming:
>
> yes known problem :/
>
> regards,
> Marc
>
> --
> Pengutronix e.K. | Marc Kleine-Budde |
> Embedded Linux | https://www.pengutronix.de |
> Vertretung Nürnberg | Phone: +49-5121-206917-129 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
>
next prev parent reply other threads:[~2026-10-12 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 9:14 [PATCH 0/5] can: peak_usb: fixes, cleanup and input validation hardening Stéphane Grosjean
2026-10-08 9:14 ` [PATCH 1/5] can: peak_usb: fix missing CAN_ERR_FLAG when reporting error counters Stéphane Grosjean
2026-10-08 9:14 ` [PATCH 2/5] can: peak_usb: add missing includes Stéphane Grosjean
2026-10-08 9:14 ` [PATCH 3/5] can: peak_usb: sort ctrlmode_supported flags Stéphane Grosjean
2026-10-08 9:14 ` [PATCH 4/5] can: peak_usb: validate channel numbers in PCAN-USB FD Stéphane Grosjean
2026-10-10 6:48 ` netdev-bot+sashiko
2026-10-12 9:04 ` Fwd: " Stéphane Grosjean
2026-10-12 12:36 ` Marc Kleine-Budde
2026-10-12 14:08 ` Stéphane Grosjean [this message]
2026-10-08 9:14 ` [PATCH 5/5] can: peak_usb: harden PCAN-USB message validation Stéphane Grosjean
2026-10-10 6:48 ` netdev-bot+sashiko
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=1228378911.1051074990.1791814127665.JavaMail.root@zimbra65-e11.priv.proxad.net \
--to=stephane.grosjean@free.fr \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
/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
all inboxes | Powered by JetHome®