From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: Colin King <colin.king@canonical.com>,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
Doug Ledford <dledford@redhat.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] IB/hfi1: fix spelling mistake: "Maximim" -> "Maximum"
Date: Tue, 8 Aug 2017 14:18:35 -0400 [thread overview]
Message-ID: <a4b6438a-bc4f-53bb-192e-559fa2ccdf24@intel.com> (raw)
In-Reply-To: <20170805131150.32717-1-colin.king@canonical.com>
On 8/5/2017 9:11 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in pr_warn_ratelimited warning message
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/infiniband/hw/hfi1/mad.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/hfi1/mad.c b/drivers/infiniband/hw/hfi1/mad.c
> index 0a3e2dfdf56e..cb0bb69310e1 100644
> --- a/drivers/infiniband/hw/hfi1/mad.c
> +++ b/drivers/infiniband/hw/hfi1/mad.c
> @@ -172,7 +172,7 @@ static struct trap_node *check_and_add_trap(struct hfi1_ibport *ibp,
> trap_list->list_len++;
> list_add_tail(&trap->list, &trap_list->list);
> } else {
> - pr_warn_ratelimited("hfi1: Maximim trap limit reached for 0x%0x traps\n",
> + pr_warn_ratelimited("hfi1: Maximum trap limit reached for 0x%0x traps\n",
> trap->data.generic_type);
> kfree(trap);
> }
>
Thanks!
Acked-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
next prev parent reply other threads:[~2017-08-08 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 13:11 [PATCH] IB/hfi1: fix spelling mistake: "Maximim" -> "Maximum" Colin King
2017-08-08 18:18 ` Dennis Dalessandro [this message]
2017-08-22 18:24 ` Doug Ledford
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=a4b6438a-bc4f-53bb-192e-559fa2ccdf24@intel.com \
--to=dennis.dalessandro@intel.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=mike.marciniszyn@intel.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