From: Markus Elfring <Markus.Elfring@web.de>
To: "Xiong Weimin" <xiongweimin@kylinos.cn>,
netdev@vger.kernel.org, virtualization@lists.linux.dev,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Jason Wang" <jasowangio@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] virtio_net: roll back RSS state on control failure
Date: Mon, 17 Aug 2026 13:13:14 +0200 [thread overview]
Message-ID: <11265d47-39c6-43cc-9115-022d464bc154@web.de> (raw)
In-Reply-To: <20260811022055.3465420-1-xiongweimin@kylinos.cn>
…
> Preserve the previous local state around RSS/hash control commands and
> restore it when the device update fails, while propagating the error to
> the caller.
How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.2-rc7#n145
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v7.2-rc7#n34
> v1 -> v2:
…
> ---
> drivers/net/virtio_net.c | 56 +++++++++++++++++++++++++++++----------
…
Please move patch version descriptions behind the marker line.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.2-rc7#n795
Regards,
Markus
next prev parent reply other threads:[~2026-08-17 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 2:20 [PATCH] virtio_net: roll back RSS state on control failure Xiong Weimin
2026-08-17 11:13 ` Markus Elfring [this message]
2026-08-17 22:29 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2026-08-11 2:19 Xiong Weimin
2026-08-11 2:22 ` Xiong Weimin
2026-08-04 7:36 Xiong Weimin
2026-08-08 1:19 ` Jakub Kicinski
2026-08-08 8:32 ` Michael S. Tsirkin
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=11265d47-39c6-43cc-9115-022d464bc154@web.de \
--to=markus.elfring@web.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xiongweimin@kylinos.cn \
--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.