mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaosheng Qu <chaosheng.qu.linux@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
	Vincent Mailhol <mailhol@kernel.org>,
	linux-can@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] can: don't discard the platform_get_irq() error in probe
Date: Sun, 25 Oct 2026 10:18:45 +0800	[thread overview]
Message-ID: <179289472574.8393.12094085935716992853@gmail.com> (raw)
In-Reply-To: <20261021133130.2cf75b3c@kernel.org>

Hi Jakub,

You are right, and thanks for pointing it out -- the Cc came from my send script,
not from `get_maintainer.pl`, and I have fixed the script so it can't happen
again.

To be explicit about what I am not doing: I am not resending. The patches
already reached the people who matter, the CAN trees are the right path for
them, and another copy in everyone's inbox would be exactly the noise you are
asking me to stop making. This is just the acknowledgement.

For the record, the same mistake went out in a second small series the same day
(`can: slcan/can327: publish tty->disc_data only after register_candev()`,
2 patches). Both were sent to linux-can@ plus the per-file people from
`get_maintainer.pl`; the extra Cc is gone from the script, so neither can repeat
it.

Sorry for the noise.

Chaosheng


      reply	other threads:[~2026-10-25  2:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  6:11 Chaosheng Qu
2026-10-16  6:11 ` [PATCH net-next 1/4] can: sun4i_can: don't discard the IRQ lookup " Chaosheng Qu
2026-10-16  6:11 ` [PATCH net-next 2/4] can: at91_can: " Chaosheng Qu
2026-10-16  6:11 ` [PATCH net-next 3/4] can: janz-ican3: " Chaosheng Qu
2026-10-16  6:11 ` [PATCH net-next 4/4] can: ifi_canfd: " Chaosheng Qu
2026-10-16  6:15 ` [PATCH net-next 0/4] can: don't discard the platform_get_irq() " netdev-bot+sinfo
2026-10-16  7:16   ` chaosheng.qu.linux
2026-10-21 20:31 ` Jakub Kicinski
2026-10-25  2:18   ` Chaosheng Qu [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=179289472574.8393.12094085935716992853@gmail.com \
    --to=chaosheng.qu.linux@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol@kernel.org \
    --cc=mkl@pengutronix.de \
    /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®