From: Jakub Kicinski <kuba@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alvaro Karsz <alvaro.karsz@solid-run.com>,
netdev@vger.kernel.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH] net: virtio_net: fix notification coalescing comments
Date: Fri, 26 Aug 2022 18:53:28 -0700 [thread overview]
Message-ID: <20220826185328.12227497@kernel.org> (raw)
In-Reply-To: <20220823073947.14774-1-alvaro.karsz@solid-run.com>
On Tue, 23 Aug 2022 10:39:47 +0300 Alvaro Karsz wrote:
> Fix wording in comments for the notifications coalescing feature.
>
> Signed-off-by: Alvaro Karsz <alvaro.karsz@solid-run.com>
> ---
> include/uapi/linux/virtio_net.h | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
Hi Michael, do we take this on or do you?
I think DaveM marked it as Not Applicable in our PW but I'm unclear
on what the split is on virtio_net, so I thought I'd ask.
next prev parent reply other threads:[~2022-08-27 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:39 [PATCH] net: virtio_net: fix notification coalescing comments Alvaro Karsz
2022-08-27 1:53 ` Jakub Kicinski [this message]
2022-08-28 10:06 ` Michael S. Tsirkin
2022-08-31 5:50 ` 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=20220826185328.12227497@kernel.org \
--to=kuba@kernel.org \
--cc=alvaro.karsz@solid-run.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
/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.