From: Jakub Raczynski <j.raczynski@samsung.com>
To: weimin xiong <15927021679@163.com>
Cc: netdev@vger.kernel.org, mst@redhat.com, jasowangio@gmail.com,
xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
virtualization@lists.linux.dev,
xiongweimin <xiongweimin@kylinos.cn>
Subject: Re: [PATCH] virtio_net: fix spelling of aggressively in comments
Date: Wed, 15 Jul 2026 10:49:46 +0200 [thread overview]
Message-ID: <aldJquLV8Up9o3X2@AMDC4622.eu.corp.samsungelectronics.net> (raw)
In-Reply-To: <20260714024037.186799-1-15927021679@163.com>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
Please read
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
This patch should target net-next tree and is not actively CC'ing any
maintainer. Use 'get_maintainer.pl' script to get correct recipents.
BR
Jakub Raczynski
On Tue, Jul 14, 2026 at 10:40:37AM +0800, weimin xiong wrote:
> From: xiongweimin <xiongweimin@kylinos.cn>
>
> Two receive-path comments misspell "aggressively" as "agressively".
>
> Signed-off-by: xiongweimin <xiongweimin@kylinos.cn>
> ---
> drivers/net/virtio_net.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> index 3e2a5876c..f3c7b28ce 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -3190,7 +3190,7 @@ static int virtnet_open(struct net_device *dev)
>
> for (i = 0; i < vi->max_queue_pairs; i++) {
> if (i < vi->curr_queue_pairs)
> - /* Pre-fill rq agressively, to make sure we are ready to
> + /* Pre-fill rq aggressively, to make sure we are ready to
> * get packets immediately.
> */
> try_fill_recv(vi, &vi->rq[i], GFP_KERNEL);
> @@ -3419,7 +3419,7 @@ static void virtnet_rx_resume(struct virtnet_info *vi,
> bool refill)
> {
> if (netif_running(vi->dev)) {
> - /* Pre-fill rq agressively, to make sure we are ready to get
> + /* Pre-fill rq aggressively, to make sure we are ready to get
> * packets immediately.
> */
> if (refill)
> --
> 2.43.0
>
>
> No virus found
> Checked by Hillstone Network AntiVirus
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2026-07-15 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260715084952eucas1p263586986449da01e2cca9851c4118919@eucas1p2.samsung.com>
2026-07-14 2:40 ` [PATCH] virtio_net: fix spelling of aggressively in comments weimin xiong
2026-07-15 8:49 ` Jakub Raczynski [this message]
2026-07-16 1:12 Weimin Xiong
2026-07-21 22:22 ` Jakub Kicinski
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=aldJquLV8Up9o3X2@AMDC4622.eu.corp.samsungelectronics.net \
--to=j.raczynski@samsung.com \
--cc=15927021679@163.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox