From: "Saleem, Shiraz" <shiraz.saleem@intel.com>
To: Colin King <colin.king@canonical.com>,
"Ismail, Mustafa" <mustafa.ismail@intel.com>,
Doug Ledford <dledford@redhat.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH][next] RDMA/irdma: Fix spelling mistake "Allocal" -> "Allocate"
Date: Mon, 7 Jun 2021 14:54:11 +0000 [thread overview]
Message-ID: <2141f5220efd4b788dc7feda1f5018d6@intel.com> (raw)
In-Reply-To: <20210605001802.15948-1-colin.king@canonical.com>
> Subject: [PATCH][next] RDMA/irdma: Fix spelling mistake "Allocal" -> "Allocate"
>
> 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/irdma/utils.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/irdma/utils.c b/drivers/infiniband/hw/irdma/utils.c
> index 2f078155d6fd..8f04347be52c 100644
> --- a/drivers/infiniband/hw/irdma/utils.c
> +++ b/drivers/infiniband/hw/irdma/utils.c
> @@ -636,7 +636,7 @@ static const char *const
> irdma_cqp_cmd_names[IRDMA_MAX_CQP_OPS] = {
> [IRDMA_OP_SET_UP_MAP] = "Set UP-UP Mapping Cmd",
> [IRDMA_OP_GEN_AE] = "Generate AE Cmd",
> [IRDMA_OP_QUERY_RDMA_FEATURES] = "RDMA Get Features Cmd",
> - [IRDMA_OP_ALLOC_LOCAL_MAC_ENTRY] = "Allocal Local MAC Entry
> Cmd",
> + [IRDMA_OP_ALLOC_LOCAL_MAC_ENTRY] = "Allocate Local MAC Entry
> Cmd",
Acked-by: Shiraz Saleem <shiraz.saleem@intel.com>
next prev parent reply other threads:[~2021-06-07 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 0:18 [PATCH][next] RDMA/irdma: Fix spelling mistake "Allocal" -> "Allocate" Colin King
2021-06-07 14:54 ` Saleem, Shiraz [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-07 11:33 Colin King
2021-06-07 23:46 ` 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=2141f5220efd4b788dc7feda1f5018d6@intel.com \
--to=shiraz.saleem@intel.com \
--cc=colin.king@canonical.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mustafa.ismail@intel.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).