From: Doug Ledford <dledford@redhat.com>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: "ira.weiny" <ira.weiny@intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Matan Barak <matanb@mellanox.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Haggai Eran <haggaie@mellanox.com>,
Michael Wang <yun.wang@profitbricks.com>,
Yotam Kenneth <yotamke@mellanox.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] IB/core: missing curly braces in ib_find_gid()
Date: Sun, 30 Aug 2015 18:24:20 -0400 [thread overview]
Message-ID: <55E38294.7040404@redhat.com> (raw)
In-Reply-To: <CAJ3xEMgSQHvATJjydeLQbvOXSuS1LNwvf7hs-tvmP77_EJ12BQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
On 08/30/2015 12:59 AM, Or Gerlitz wrote:
> On Fri, Aug 28, 2015 at 9:02 PM, Doug Ledford <dledford@redhat.com> wrote:
>> On 08/28/2015 09:10 PM, ira.weiny wrote:
>>> On Tue, Aug 18, 2015 at 12:22:10PM +0300, Dan Carpenter wrote:
>>>> Smatch says that, based on the indenting, we should probably add curly
>>>> braces here.
>>>>
>>>> Fixes: 230145ff8124 ('IB/core: Add RoCE GID table management')
>>>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>>>>
>>>
>>> Reviewed-by: Ira Weiny <ira.weiny@intel.com>
>>
>> I've picked this patch up (earlier today), so I missed your reviewed-by:
>> tag. Added.
>
> wait, Doug, when the offending patch goes upstream, their commit ID
> will not be the one
> denoted here, right?
Fair point...
> I would suggest that you either hold off with
> this fix till the other patch
> goes upstream in 4,3-rc1 and you have a proper ID
I have a proper ID now. Since I've put together my final k.o/for-4.3
branch, the ID is fixed.
> or squash it there
> now.
This patch is from someone different than the patch it fixes, so it
wouldn't be right to squash it into their patch. I fixed up the Fixes:
line instead.
> BTW - the way
> net-next is organized/managed, pre-linus-tree commit ID remain the
> same also after they land there,
> so in that respect and other linux-rdma maintenance related aspects we
> discussed during LPC - it
> would be good if you can talk to Dave and see how he gets things going
> for net-next
I'm going to be doing things differently for 4.4. We'll see if that
resolves the issues you are unhappy about.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2015-08-30 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 9:22 [patch] IB/core: missing curly braces in ib_find_gid() Dan Carpenter
2015-08-29 1:10 ` ira.weiny
[not found] ` <20150829011040.GA2713-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2015-08-29 4:02 ` Doug Ledford
2015-08-30 4:59 ` Or Gerlitz
2015-08-30 22:24 ` Doug Ledford [this message]
2015-09-03 17:39 ` 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=55E38294.7040404@redhat.com \
--to=dledford@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=gerlitz.or@gmail.com \
--cc=haggaie@mellanox.com \
--cc=hal.rosenstock@gmail.com \
--cc=ira.weiny@intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=sean.hefty@intel.com \
--cc=yotamke@mellanox.com \
--cc=yun.wang@profitbricks.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).