From: Colin Ian King <colin.king@canonical.com>
To: Doug Ledford <dledford@redhat.com>, Joe Perches <joe@perches.com>,
Moni Shoua <monis@mellanox.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
linux-rdma@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][V2] IB/rxe: fix typo: "algorithmi" -> "algorithm"
Date: Fri, 28 Apr 2017 18:14:53 +0100 [thread overview]
Message-ID: <ee6de221-24f0-bbb5-d684-a50aef0a73dc@canonical.com> (raw)
In-Reply-To: <1493399309.3041.158.camel@redhat.com>
On 28/04/17 18:08, Doug Ledford wrote:
> On Mon, 2017-04-24 at 10:44 -0700, Joe Perches wrote:
>> On Mon, 2017-04-24 at 10:26 +0100, Colin King wrote:
>>>
>>> trivial fix to typo in pr_err message
>> []
>>>
>>> diff --git 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",
>>
>> nicer to add a newline too
>
> I added a newline and then applied the patch. Thanks.
>
Thanks Doug. I overlooked replying to the earlier email.
Colin
prev parent reply other threads:[~2017-04-28 17:15 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
2017-04-24 17:44 ` Joe Perches
2017-04-28 17:08 ` Doug Ledford
2017-04-28 17:14 ` Colin Ian King [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=ee6de221-24f0-bbb5-d684-a50aef0a73dc@canonical.com \
--to=colin.king@canonical.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=monis@mellanox.com \
--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).