From: Jakub Kicinski <kuba@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Paolo Abeni <pabeni@redhat.com>,
Ming Wang <wangming01@loongson.cn>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
stable@vger.kernel.org, Oliver Neukum <oliver@neukum.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: usb: cdc_mbim: add MeiG Smart SRM821 to ZLP whitelist
Date: Thu, 24 Sep 2026 09:28:51 -0700 [thread overview]
Message-ID: <20260924092851.33737b1e@kernel.org> (raw)
In-Reply-To: <2026092409-status-rocker-0fef@gregkh>
On Thu, 24 Sep 2026 16:22:54 +0200 Greg KH wrote:
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Ming Wang <wangming01@loongson.cn>
> >
> > Before any other step, please read:
> >
> > https://elixir.bootlin.com/linux/v7.3-rc3/source/Documentation/process/maintainer-netdev.rst#L454
> >
> > AFAICS this is actually support for additional H/W, just worded in
> > very unusual way: please reword the commit message accordingly and
> > drop stable from CC.
>
> Why drop stable from cc:? Do you not want it in any stable kernel
> release? Seems like it should be to me, we gladly take quirk additions
> and new device ids in stable kernels.
the irony of telling someone to RTFM while not reading
someone else's FM :)
next prev parent reply other threads:[~2026-09-24 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 7:44 [PATCH v2] net: usb: cdc_mbim: add MeiG Smart SRM821 to ZLP whitelist Ming Wang
2026-09-24 10:24 ` Paolo Abeni
2026-09-24 14:22 ` Greg KH
2026-09-24 16:28 ` Jakub Kicinski [this message]
2026-09-25 5:12 ` Greg KH
2026-09-25 20:23 ` Jakub Kicinski
2026-09-24 16:30 ` patchwork-bot+netdevbpf
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=20260924092851.33737b1e@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=wangming01@loongson.cn \
/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.