public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Prabhav Kumar Vaish <pvkumar5749404@gmail.com>
Cc: shuah@kernel.org, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	petrm@nvidia.com, idosch@nvidia.com
Subject: Re: [PATCH] Correcting the spelling mistake in selftests drivers/net testing
Date: Wed, 28 Feb 2024 08:50:02 +0100	[thread overview]
Message-ID: <Zd7lqr8Cz4XrNoI8@nanopsycho> (raw)
In-Reply-To: <20240227175513.8703-1-pvkumar5749404@gmail.com>

Please fix the patch subject to include appropriate prefixes and
rephrase a bit like this:

Subject: [PATCH net-next] selftests: net: Correct couple of spelling mistakes

pw-bot: cr


Tue, Feb 27, 2024 at 06:55:13PM CET, pvkumar5749404@gmail.com wrote:
>Changes :
>	- "excercise" is corrected to "exercise" in drivers/net/mlxsw/spectrum-2/tc_flower.sh
>	- "mutliple" is corrected to "multiple" in drivers/net/netdevsim/ethtool-fec.sh
>
>Signed-off-by: Prabhav Kumar Vaish <pvkumar5749404@gmail.com>
>---
> .../testing/selftests/drivers/net/mlxsw/spectrum-2/tc_flower.sh | 2 +-
> tools/testing/selftests/drivers/net/netdevsim/ethtool-fec.sh    | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/tools/testing/selftests/drivers/net/mlxsw/spectrum-2/tc_flower.sh b/tools/testing/selftests/drivers/net/mlxsw/spectrum-2/tc_flower.sh
>index 616d3581419c..31252bc8775e 100755
>--- a/tools/testing/selftests/drivers/net/mlxsw/spectrum-2/tc_flower.sh
>+++ b/tools/testing/selftests/drivers/net/mlxsw/spectrum-2/tc_flower.sh
>@@ -869,7 +869,7 @@ bloom_simple_test()
> bloom_complex_test()
> {
> 	# Bloom filter index computation is affected from region ID, eRP
>-	# ID and from the region key size. In order to excercise those parts
>+	# ID and from the region key size. In order to exercise those parts
> 	# of the Bloom filter code, use a series of regions, each with a
> 	# different key size and send packet that should hit all of them.
> 	local index
>diff --git a/tools/testing/selftests/drivers/net/netdevsim/ethtool-fec.sh b/tools/testing/selftests/drivers/net/netdevsim/ethtool-fec.sh
>index 7d7829f57550..6c52ce1b0450 100755
>--- a/tools/testing/selftests/drivers/net/netdevsim/ethtool-fec.sh
>+++ b/tools/testing/selftests/drivers/net/netdevsim/ethtool-fec.sh
>@@ -49,7 +49,7 @@ for o in llrs rs; do
> Active FEC encoding: ${o^^}"
> done
> 
>-# Test mutliple bits
>+# Test multiple bits
> $ETHTOOL --set-fec $NSIM_NETDEV encoding rs llrs
> check $?
> s=$($ETHTOOL --show-fec $NSIM_NETDEV | tail -2)
>-- 
>2.34.1
>
>

  reply	other threads:[~2024-02-28  7:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 17:55 [PATCH] Correcting the spelling mistake in selftests drivers/net testing Prabhav Kumar Vaish
2024-02-28  7:50 ` Jiri Pirko [this message]
2024-02-28  8:37   ` [PATCH net-next] selftests: net: Correctcouple of spelling mistakes prabhav kumar
2024-02-28  8:42   ` [PATCH net-next] selftests: net: Correct couple " prabhav kumar
2024-02-28  9:32     ` Jiri Pirko
2024-02-28 12:37       ` prabhav kumar

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=Zd7lqr8Cz4XrNoI8@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=idosch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.com \
    --cc=pvkumar5749404@gmail.com \
    --cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox