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>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/qib: fix spelling mistake "colescing" -> "coalescing"
Date: Mon, 26 Nov 2018 16:05:05 -0500 [thread overview]
Message-ID: <d671a718-1267-19c6-0aef-4256a0e6ecfb@intel.com> (raw)
In-Reply-To: <20181126162320.27889-1-colin.king@canonical.com>
On 11/26/2018 11:23 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in the module description text, fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/infiniband/hw/qib/qib_pcie.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/qib/qib_pcie.c b/drivers/infiniband/hw/qib/qib_pcie.c
> index 30595b358d8f..864f2af171f7 100644
> --- a/drivers/infiniband/hw/qib/qib_pcie.c
> +++ b/drivers/infiniband/hw/qib/qib_pcie.c
> @@ -387,7 +387,7 @@ void qib_pcie_reenable(struct qib_devdata *dd, u16 cmd, u8 iline, u8 cline)
>
> static int qib_pcie_coalesce;
> module_param_named(pcie_coalesce, qib_pcie_coalesce, int, S_IRUGO);
> -MODULE_PARM_DESC(pcie_coalesce, "tune PCIe colescing on some Intel chipsets");
> +MODULE_PARM_DESC(pcie_coalesce, "tune PCIe coalescing on some Intel chipsets");
>
> /*
> * Enable PCIe completion and data coalescing, on Intel 5x00 and 7300
>
Thanks!
Reviewed-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
next prev parent reply other threads:[~2018-11-26 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 16:23 [PATCH] IB/qib: fix spelling mistake "colescing" -> "coalescing" Colin King
2018-11-26 21:05 ` Dennis Dalessandro [this message]
2018-11-26 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=d671a718-1267-19c6-0aef-4256a0e6ecfb@intel.com \
--to=dennis.dalessandro@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=mike.marciniszyn@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