From: Doug Ledford <dledford@redhat.com>
To: Colin King <colin.king@canonical.com>,
Yishai Hadas <yishaih@mellanox.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Jiri Kosina <trivial@kernel.org>,
linux-rdma@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/mlx4: trivial fix of spelling mistake on "argument"
Date: Fri, 13 May 2016 15:34:56 -0400 [thread overview]
Message-ID: <712fbfbf-dce1-f5a2-380a-fa2843813f7b@redhat.com> (raw)
In-Reply-To: <1461612410-27604-1-git-send-email-colin.king@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
On 04/25/2016 03:26 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> fix spelling mistake, argumant -> argument
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/infiniband/hw/mlx4/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/mlx4/main.c b/drivers/infiniband/hw/mlx4/main.c
> index f014eaf..b01ef6e 100644
> --- a/drivers/infiniband/hw/mlx4/main.c
> +++ b/drivers/infiniband/hw/mlx4/main.c
> @@ -1601,7 +1601,7 @@ static int __mlx4_ib_create_flow(struct ib_qp *qp, struct ib_flow_attr *flow_att
> else if (ret == -ENXIO)
> pr_err("Device managed flow steering is disabled. Fail to register network rule.\n");
> else if (ret)
> - pr_err("Invalid argumant. Fail to register network rule.\n");
> + pr_err("Invalid argument. Fail to register network rule.\n");
>
> mlx4_free_cmd_mailbox(mdev->dev, mailbox);
> return ret;
>
Thanks, applied.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
prev parent reply other threads:[~2016-05-13 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 19:26 [PATCH] IB/mlx4: trivial fix of spelling mistake on "argument" Colin King
2016-04-25 20:04 ` Bart Van Assche
2016-05-13 19:34 ` Doug Ledford [this message]
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=712fbfbf-dce1-f5a2-380a-fa2843813f7b@redhat.com \
--to=dledford@redhat.com \
--cc=colin.king@canonical.com \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sean.hefty@intel.com \
--cc=trivial@kernel.org \
--cc=yishaih@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).