From: Dennis Dalessandro <dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Marciniszyn,
Mike" <mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 4/6] IB/hfi1: Fix indentation
Date: Fri, 3 Jun 2016 15:26:39 -0400 [thread overview]
Message-ID: <20160603192638.GA946@phlsvsds.ph.intel.com> (raw)
In-Reply-To: <54ad6b3b-4185-9345-26d0-ab3fd9ce36e4-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
On Fri, Jun 03, 2016 at 12:09:56PM -0700, Bart Van Assche wrote:
> #define C_MAX_NAME 13 /* 12 chars + one for /0 */
>diff --git a/drivers/infiniband/hw/hfi1/init.c b/drivers/infiniband/hw/hfi1/init.c
>index 5cc492e..0d28a5a 100644
>--- a/drivers/infiniband/hw/hfi1/init.c
>+++ b/drivers/infiniband/hw/hfi1/init.c
>@@ -1337,7 +1337,7 @@ static void cleanup_device_data(struct hfi1_devdata *dd)
> dma_free_coherent(&dd->pcidev->dev, sizeof(u64),
> (void *)dd->rcvhdrtail_dummy_kvaddr,
> dd->rcvhdrtail_dummy_physaddr);
>- dd->rcvhdrtail_dummy_kvaddr = NULL;
>+ dd->rcvhdrtail_dummy_kvaddr = NULL;
> }
>
> for (ctxt = 0; tmp && ctxt < dd->num_rcv_contexts; ctxt++) {
This is the same thing as a patch from Dan Carpenter I think?
https://patchwork.kernel.org/patch/9139133/
-Denny
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-03 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 19:07 [PATCH 0/6] Various fixes for warnings reported by static source code analysis tools Bart Van Assche
[not found] ` <86c06ca1-753c-6b45-3f65-f9a19f7693cf-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-06-03 19:08 ` [PATCH 1/6] RDMA/core: Fix indentation Bart Van Assche
[not found] ` <90c52b83-52cc-c953-babb-3f95759ca797-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-06-03 19:11 ` Steve Wise
2016-06-06 11:20 ` Sagi Grimberg
2016-06-03 19:08 ` [PATCH 2/6] IB/mad: " Bart Van Assche
[not found] ` <8eccc2e6-d33b-6130-2460-86a1d67159ae-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-06-03 19:10 ` Weiny, Ira
2016-06-03 19:13 ` Hal Rosenstock
2016-06-06 11:20 ` Sagi Grimberg
2016-06-03 19:09 ` [PATCH 3/6] IB/rdmavt: Annotate rvt_reset_qp() Bart Van Assche
2016-06-03 19:09 ` [PATCH 4/6] IB/hfi1: Fix indentation Bart Van Assche
[not found] ` <54ad6b3b-4185-9345-26d0-ab3fd9ce36e4-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-06-03 19:26 ` Dennis Dalessandro [this message]
[not found] ` <20160603192638.GA946-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2016-06-03 19:53 ` Bart Van Assche
2016-06-03 19:10 ` [PATCH 5/6] IB/hfi1: Use bit 0 instead of bit 1 Bart Van Assche
2016-06-03 19:11 ` [PATCH 6/6] IB/hfi1: Suppress sparse warnings Bart Van Assche
2016-06-06 23:38 ` [PATCH 0/6] Various fixes for warnings reported by static source code analysis tools 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=20160603192638.GA946@phlsvsds.ph.intel.com \
--to=dennis.dalessandro-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.