From: "Jürgen Groß" <jgross@suse.com>
To: Chu Guangqing <chuguangqing@inspur.com>,
sstabellini@kernel.org, oleksandr_tyshchenko@epam.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: xen-devel@lists.xenproject.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/netfront: Comment Correction: Fix Spelling Error and Description of Queue Quantity Rules
Date: Mon, 3 Nov 2025 14:19:36 +0100 [thread overview]
Message-ID: <209fa1c0-f6f2-4594-a2ae-7733ff651761@suse.com> (raw)
In-Reply-To: <20251103032212.2462-1-chuguangqing@inspur.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 930 bytes --]
On 03.11.25 04:22, Chu Guangqing wrote:
> The original comments contained spelling errors and incomplete logical
> descriptions, which could easily lead to misunderstandings of the code
> logic. The specific modifications are as follows:
>
> Correct the spelling error by changing "inut max" to "but not exceed the
> maximum limit";
>
> Add the note "If the user has not specified a value, the default maximum
> limit is 8" to clarify the default value logic;
>
> Improve the coherence of the statement to make the queue quantity rules
> clearer.
>
> After the modification, the comments can accurately reflect the code
> behavior of "taking the smaller value between the number of CPUs and the
> default maximum limit of 8 for the number of queues", enhancing code
> maintainability.
>
> Signed-off-by: Chu Guangqing <chuguangqing@inspur.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-11-03 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 3:22 Chu Guangqing
2025-11-03 13:19 ` Jürgen Groß [this message]
2025-11-05 1:10 ` 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=209fa1c0-f6f2-4594-a2ae-7733ff651761@suse.com \
--to=jgross@suse.com \
--cc=andrew+netdev@lunn.ch \
--cc=chuguangqing@inspur.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=pabeni@redhat.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®