mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
	shuah@kernel.org, linux-kernel@vger.kernel.org,
	jiri@mellanox.com, idosch@mellanox.com,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests: mlxsw: Fix typo in qos_mc_aware.sh
Date: Wed, 24 Jul 2019 07:45:59 -0700	[thread overview]
Message-ID: <3a7ae37c-36b8-74bb-4537-c87cee8ea410@infradead.org> (raw)
In-Reply-To: <20190724141554.31723-1-standby24x7@gmail.com>

On 7/24/19 7:15 AM, Masanari Iida wrote:
> This patch fixes some spelling typo in qos_mc_aware.sh
> 
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
>  tools/testing/selftests/drivers/net/mlxsw/qos_mc_aware.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/drivers/net/mlxsw/qos_mc_aware.sh b/tools/testing/selftests/drivers/net/mlxsw/qos_mc_aware.sh
> index 71231ad2dbfb..47315fe48d5a 100755
> --- a/tools/testing/selftests/drivers/net/mlxsw/qos_mc_aware.sh
> +++ b/tools/testing/selftests/drivers/net/mlxsw/qos_mc_aware.sh
> @@ -262,7 +262,7 @@ test_mc_aware()
>  
>  	stop_traffic
>  
> -	log_test "UC performace under MC overload"
> +	log_test "UC performance under MC overload"
>  
>  	echo "UC-only throughput  $(humanize $ucth1)"
>  	echo "UC+MC throughput    $(humanize $ucth2)"
> @@ -316,7 +316,7 @@ test_uc_aware()
>  
>  	stop_traffic
>  
> -	log_test "MC performace under UC overload"
> +	log_test "MC performance under UC overload"
>  	echo "    ingress UC throughput $(humanize ${uc_ir})"
>  	echo "    egress UC throughput  $(humanize ${uc_er})"
>  	echo "    sent $attempts BC ARPs, got $passes responses"
> 


-- 
~Randy

  reply	other threads:[~2019-07-24 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 14:15 Masanari Iida
2019-07-24 14:45 ` Randy Dunlap [this message]
2019-07-24 15:00 ` Ido Schimmel

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=3a7ae37c-36b8-74bb-4537-c87cee8ea410@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=standby24x7@gmail.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

all inboxes | Powered by JetHome®