public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Chu Guangqing <chuguangqing@inspur.com>, <andrew+netdev@lunn.ch>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] veth: Fix a typo error in veth
Date: Mon, 3 Nov 2025 15:43:27 -0800	[thread overview]
Message-ID: <ca1b271d-47d6-46d9-a87b-bbfd4c9eb0a3@intel.com> (raw)
In-Reply-To: <20251103055351.3150-1-chuguangqing@inspur.com>


[-- Attachment #1.1: Type: text/plain, Size: 927 bytes --]



On 11/2/2025 9:53 PM, Chu Guangqing wrote:
> Fix a spellling error for resources
> 
> Signed-off-by: Chu Guangqing <chuguangqing@inspur.com>

Typically the tags should include the target tree. Since this doesn't
impact the functionality, net-next makes the most sense to me.

Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>

> ---
>  drivers/net/veth.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/veth.c b/drivers/net/veth.c
> index a3046142cb8e..87a63c4bee77 100644
> --- a/drivers/net/veth.c
> +++ b/drivers/net/veth.c
> @@ -1323,7 +1323,7 @@ static int veth_set_channels(struct net_device *dev,
>  		if (peer)
>  			netif_carrier_off(peer);
>  
> -		/* try to allocate new resurces, as needed*/
> +		/* try to allocate new resources, as needed*/
>  		err = veth_enable_range_safe(dev, old_rx_count, new_rx_count);
>  		if (err)
>  			goto out;


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2025-11-03 23:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  5:53 [PATCH] veth: Fix a typo error in veth Chu Guangqing
2025-11-03 23:43 ` Jacob Keller [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=ca1b271d-47d6-46d9-a87b-bbfd4c9eb0a3@intel.com \
    --to=jacob.e.keller@intel.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=pabeni@redhat.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