From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
mw@semihalf.com, linux@armlinux.org.uk, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, gustavo@embeddedor.com
Subject: Re: [PATCH V3] drivers: net: marvell: Fixed two spellings,controling to controlling and oen to one
Date: Tue, 12 Jan 2021 09:26:48 -0800 [thread overview]
Message-ID: <2cf30ec7-07cc-650c-d94b-a9cd7aadb906@infradead.org> (raw)
In-Reply-To: <20210112103152.13222-1-unixbhaskar@gmail.com>
On 1/12/21 2:31 AM, Bhaskar Chowdhury wrote:
> s/oen/one/
> s/controling/controlling/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Changes from V2 : Correct the versioning,mentioned both the changes
>
> drivers/net/ethernet/marvell/mvpp2/mvpp2_cls.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/marvell/mvpp2/mvpp2_cls.h b/drivers/net/ethernet/marvell/mvpp2/mvpp2_cls.h
> index 8867f25afab4..663157dc8062 100644
> --- a/drivers/net/ethernet/marvell/mvpp2/mvpp2_cls.h
> +++ b/drivers/net/ethernet/marvell/mvpp2/mvpp2_cls.h
> @@ -143,7 +143,7 @@ struct mvpp2_cls_c2_entry {
> /* Number of per-port dedicated entries in the C2 TCAM */
> #define MVPP22_CLS_C2_PORT_N_FLOWS MVPP2_N_RFS_ENTRIES_PER_FLOW
>
> -/* Each port has oen range per flow type + one entry controling the global RSS
> +/* Each port has one range per flow type + one entry controlling the global RSS
> * setting and the default rx queue
> */
> #define MVPP22_CLS_C2_PORT_RANGE (MVPP22_CLS_C2_PORT_N_FLOWS + 1)
> ./--
> 2.26.2
>
--
~Randy
next prev parent reply other threads:[~2021-01-12 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 10:31 [PATCH V3] drivers: net: marvell: Fixed two spellings,controling to controlling and oen to one Bhaskar Chowdhury
2021-01-12 17:26 ` Randy Dunlap [this message]
2021-01-13 23:36 ` Jakub Kicinski
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=2cf30ec7-07cc-650c-d94b-a9cd7aadb906@infradead.org \
--to=rdunlap@infradead.org \
--cc=davem@davemloft.net \
--cc=gustavo@embeddedor.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=unixbhaskar@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;
as well as URLs for NNTP newsgroup(s).