linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moni Shoua <monis@mellanox.com>
To: Colin King <colin.king@canonical.com>
Cc: Doug Ledford <dledford@redhat.com>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][V2] IB/rxe: fix typo: "algorithmi" -> "algorithm"
Date: Mon, 24 Apr 2017 12:41:23 +0300	[thread overview]
Message-ID: <CAG9sBKO1S_44izyYuZsL_kLED2kxCnjnKzQDHPzLstLQjJXxuA@mail.gmail.com> (raw)
In-Reply-To: <20170424092642.29862-1-colin.king@canonical.com>

On Mon, Apr 24, 2017 at 12:26 PM, Colin King <colin.king@canonical.com> wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> trivial fix to typo in pr_err message
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/infiniband/sw/rxe/rxe_verbs.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c b/drivers/infiniband/sw/rxe/rxe_verbs.c
> index 486035a85bac..6a4b02470d21 100644
> --- a/drivers/infiniband/sw/rxe/rxe_verbs.c
> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.c
> @@ -1324,7 +1324,7 @@ int rxe_register_device(struct rxe_dev *rxe)
>
>         rxe->tfm = crypto_alloc_shash("crc32", 0, 0);
>         if (IS_ERR(rxe->tfm)) {
> -               pr_err("failed to allocate crc algorithmi err:%ld",
> +               pr_err("failed to allocate crc algorithm err:%ld",
>                        PTR_ERR(rxe->tfm));
>                 return PTR_ERR(rxe->tfm);
>         }
> --
> 2.11.0

Thanks (for both patches)

  reply	other threads:[~2017-04-24  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24  9:26 [PATCH][V2] IB/rxe: fix typo: "algorithmi" -> "algorithm" Colin King
2017-04-24  9:41 ` Moni Shoua [this message]
2017-04-24 17:44 ` Joe Perches
2017-04-28 17:08   ` Doug Ledford
2017-04-28 17:14     ` Colin Ian King

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=CAG9sBKO1S_44izyYuZsL_kLED2kxCnjnKzQDHPzLstLQjJXxuA@mail.gmail.com \
    --to=monis@mellanox.com \
    --cc=colin.king@canonical.com \
    --cc=dledford@redhat.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sean.hefty@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).