From: Jason Gunthorpe <jgg@mellanox.com>
To: Colin King <colin.king@canonical.com>
Cc: Selvin Xavier <selvin.xavier@broadcom.com>,
Devesh Sharma <devesh.sharma@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>,
Doug Ledford <dledford@redhat.com>,
"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] RDMA/bnxt_re: fix spelling mistake "missin_resp" -> "missing_resp"
Date: Thu, 12 Sep 2019 15:10:12 +0000 [thread overview]
Message-ID: <20190912150957.GA9160@mellanox.com> (raw)
In-Reply-To: <20190911092856.11146-1-colin.king@canonical.com>
On Wed, Sep 11, 2019 at 10:28:56AM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a literal string, fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/infiniband/hw/bnxt_re/hw_counters.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/bnxt_re/hw_counters.c b/drivers/infiniband/hw/bnxt_re/hw_counters.c
> index 604b71875f5f..3421a0b15983 100644
> --- a/drivers/infiniband/hw/bnxt_re/hw_counters.c
> +++ b/drivers/infiniband/hw/bnxt_re/hw_counters.c
> @@ -74,7 +74,7 @@ static const char * const bnxt_re_stat_name[] = {
> [BNXT_RE_SEQ_ERR_NAKS_RCVD] = "seq_err_naks_rcvd",
> [BNXT_RE_MAX_RETRY_EXCEEDED] = "max_retry_exceeded",
> [BNXT_RE_RNR_NAKS_RCVD] = "rnr_naks_rcvd",
> - [BNXT_RE_MISSING_RESP] = "missin_resp",
> + [BNXT_RE_MISSING_RESP] = "missing_resp",
Broadcom folks, can you confirm if this is OK? Is the string ABI for
this driver?
Jason
next prev parent reply other threads:[~2019-09-12 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 9:28 [PATCH] RDMA/bnxt_re: fix spelling mistake "missin_resp" -> "missing_resp" Colin King
2019-09-11 9:28 ` Colin King
2019-09-12 15:10 ` Jason Gunthorpe [this message]
2019-09-13 9:55 ` Selvin Xavier
2019-09-13 9:56 ` Selvin Xavier
2019-09-16 14:00 ` Jason Gunthorpe
2019-09-16 14:00 ` Jason Gunthorpe
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=20190912150957.GA9160@mellanox.com \
--to=jgg@mellanox.com \
--cc=colin.king@canonical.com \
--cc=devesh.sharma@broadcom.com \
--cc=dledford@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.