From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: <UNGLinuxDriver@microchip.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, <netdev@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] net: lan966x: Fix spelling mistake "tarffic" -> "traffic"
Date: Wed, 28 Sep 2022 20:28:08 +0200 [thread overview]
Message-ID: <20220928182808.gsfwyjlmunxl7k6z@soft-dev3-1.localhost> (raw)
In-Reply-To: <20220928143618.34947-1-colin.i.king@gmail.com>
The 09/28/2022 15:36, Colin Ian King wrote:
>
> There is a spelling mistake in a netdev_err message. Fix it.
Reviewed-by: Horatiu Vultur <horatiu.vultur@microchip.com>
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/net/ethernet/microchip/lan966x/lan966x_mqprio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/microchip/lan966x/lan966x_mqprio.c b/drivers/net/ethernet/microchip/lan966x/lan966x_mqprio.c
> index 950ea4807eb6..7fa76e74f9e2 100644
> --- a/drivers/net/ethernet/microchip/lan966x/lan966x_mqprio.c
> +++ b/drivers/net/ethernet/microchip/lan966x/lan966x_mqprio.c
> @@ -7,7 +7,7 @@ int lan966x_mqprio_add(struct lan966x_port *port, u8 num_tc)
> u8 i;
>
> if (num_tc != NUM_PRIO_QUEUES) {
> - netdev_err(port->dev, "Only %d tarffic classes supported\n",
> + netdev_err(port->dev, "Only %d traffic classes supported\n",
> NUM_PRIO_QUEUES);
> return -EINVAL;
> }
> --
> 2.37.1
>
--
/Horatiu
next prev parent reply other threads:[~2022-09-28 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 14:36 [PATCH][next] net: lan966x: Fix spelling mistake "tarffic" -> "traffic" Colin Ian King
2022-09-28 18:28 ` Horatiu Vultur [this message]
2022-09-30 11:40 ` 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=20220928182808.gsfwyjlmunxl7k6z@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=colin.i.king@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--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