From: Simon Horman <horms@kernel•org>
To: Abhilekh Deka <abhindeka@gmail•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
nnac123@linux•ibm.com, maddy@linux•ibm.com, mpe@ellerman•id.au,
linuxppc-dev@lists•ozlabs.org, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH v2] net/ibmveth: fix comment typos in imbveth.c
Date: Wed, 25 Feb 2026 19:35:45 +0000 [thread overview]
Message-ID: <aZ9PEaog5ZMr7LqW@horms.kernel.org> (raw)
In-Reply-To: <20260224153101.16935-1-abhindeka@gmail.com>
On Tue, Feb 24, 2026 at 09:01:01PM +0530, Abhilekh Deka wrote:
> Correct spelling mistakes in comments:
> - Fix misspelling of gro_receive
> - Fix misspelling of Partition
>
> Signed-off-by: Abhilekh Deka <abhindeka@gmail•com>
Thanks for the update.
Reviewed-by: Simon Horman <horms@kernel•org>
prev parent reply other threads:[~2026-02-25 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 15:31 [PATCH v2] net/ibmveth: fix comment typos in imbveth.c Abhilekh Deka
2026-02-25 19:35 ` Simon Horman [this message]
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=aZ9PEaog5ZMr7LqW@horms.kernel.org \
--to=horms@kernel$(echo .)org \
--cc=abhindeka@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nnac123@linux$(echo .)ibm.com \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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