From: Dan Carpenter <dan.carpenter@oracle.com>
To: Tariq Toukan <tariqt@mellanox.com>
Cc: Colin King <colin.king@canonical.com>,
"David S . Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/mlx4_en: fix spelling mistake: "quiting" -> "quitting"
Date: Mon, 18 Feb 2019 13:25:57 +0300 [thread overview]
Message-ID: <20190218102557.GC17104@kadam> (raw)
In-Reply-To: <2a1a6636-7795-addb-d7b7-711a23dbafa5@mellanox.com>
On Mon, Feb 18, 2019 at 09:37:22AM +0000, Tariq Toukan wrote:
>
>
> On 2/18/2019 1:03 AM, Colin King wrote:
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > There is a spelling mistake in a en_err error message. Fix it.
> >
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > ---
> > drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
> > index 6b88881b8e35..c1438ae52a11 100644
> > --- a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
> > +++ b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
> > @@ -3360,7 +3360,7 @@ int mlx4_en_init_netdev(struct mlx4_en_dev *mdev, int port,
> > dev->addr_len = ETH_ALEN;
> > mlx4_en_u64_to_mac(dev->dev_addr, mdev->dev->caps.def_mac[priv->port]);
> > if (!is_valid_ether_addr(dev->dev_addr)) {
> > - en_err(priv, "Port: %d, invalid mac burned: %pM, quiting\n",
> > + en_err(priv, "Port: %d, invalid mac burned: %pM, quitting\n",
> > priv->port, dev->dev_addr);
> > err = -EINVAL;
> > goto out;
> >
>
> Hi Colin, thanks for your patch.
>
> Reviewed-by: Tariq Toukan <tariqt@mellanox.com>
>
> I would suggest adding a Fixes line, but looking into the history of the
> typo, it went through many patches that modified this line but preserved
> the typo.
> Actually, it dates back to the very first commit that introduces mlx4
> driver:
>
> Patches history:
> 2b3ddf27f48c net/mlx4_core: Replace VF zero mac with random mac in mlx4_core
> ef96f7d46ad8 net/mlx4_en: Handle unassigned VF MAC address correctly
> 6bbb6d99f3d2 net/mlx4_en: Optimize Rx fast path filter checks
> 453a60827735 mlx4_en: Giving interface name in debug messages
> c27a02cd94d6 mlx4_en: Add driver for Mellanox ConnectX 10GbE NIC
>
> I'm not sure what the "Fixes:" policy is in these cases.
I wouldn't necessarily put a Fixes tag on this, because does fixing the
spelling really count as a bugfix? It's borderline whether it's a fix
or a cleanup.
regards,
daan carpenter
next prev parent reply other threads:[~2019-02-18 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 23:03 [PATCH] net/mlx4_en: fix spelling mistake: "quiting" -> "quitting" Colin King
2019-02-18 9:37 ` Tariq Toukan
2019-02-18 10:25 ` Dan Carpenter [this message]
2019-02-18 14:54 ` Tariq Toukan
2019-02-18 20:08 ` David Miller
2019-02-19 8:20 ` Tariq Toukan
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=20190218102557.GC17104@kadam \
--to=dan.carpenter@oracle.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tariqt@mellanox.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).