From: Jakub Kicinski <kuba@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Breno Leitao <leitao@debian.org>,
hengqi@linux.alibaba.com, xuanzhuo@linux.alibaba.com,
Jason Wang <jasowang@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Melnychenko <andrew@daynix.com>,
rbc@meta.com, riel@surriel.com, stable@vger.kernel.org,
qemu-devel@nongnu.org,
"open list:VIRTIO CORE AND NET DRIVERS"
<virtualization@lists.linux.dev>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v3] virtio_net: Do not send RSS key if it is not supported
Date: Mon, 1 Apr 2024 08:20:59 -0700 [thread overview]
Message-ID: <20240401082059.77df2ff0@kernel.org> (raw)
In-Reply-To: <20240331160618-mutt-send-email-mst@kernel.org>
On Sun, 31 Mar 2024 16:20:30 -0400 Michael S. Tsirkin wrote:
> > Fixes: c7114b1249fa ("drivers/net/virtio_net: Added basic RSS support.")
> > Cc: stable@vger.kernel.org
>
> net has its own stable process, don't CC stable on net patches.
Not any more, FWIW:
1.5.7. Stable tree
While it used to be the case that netdev submissions were not
supposed to carry explicit CC: stable@vger.kernel.org tags that is no
longer the case today. Please follow the standard stable rules in
Documentation/process/stable-kernel-rules.rst, and make sure you
include appropriate Fixes tags!
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#stable-tree
next prev parent reply other threads:[~2024-04-01 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 17:16 [PATCH net v3] virtio_net: Do not send RSS key if it is not supported Breno Leitao
2024-03-31 13:22 ` Heng Qi
2024-03-31 20:20 ` Michael S. Tsirkin
2024-04-01 15:20 ` Jakub Kicinski [this message]
2024-04-03 7:57 ` Heng Qi
2024-04-03 12:53 ` Breno Leitao
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=20240401082059.77df2ff0@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@daynix.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rbc@meta.com \
--cc=riel@surriel.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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.