From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Hal Rosenstock
<hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Christoph Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>,
"Weiny, Ira" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Matan Barak
<matanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2] IB/core: sysfs.c: Fix PerfMgt ClassPortInfo handling
Date: Tue, 19 Jan 2016 16:21:14 -0500 [thread overview]
Message-ID: <569EA8CA.3030304@redhat.com> (raw)
In-Reply-To: <569EA8B2.80607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
On 01/19/2016 04:20 PM, Doug Ledford wrote:
> On 12/29/2015 07:46 AM, Hal Rosenstock wrote:
>> On 12/29/2015 7:21 AM, Or Gerlitz wrote:
>>> On 12/29/2015 12:43 PM, Hal Rosenstock wrote:
>>>> This handles issue pointed out by Matan Barak <matanb-LDSdmyG8hGXFtvusC2JeyQ@public.gmane.orgo.il>
>>>>
>>>> Fixes: 145d9c541032 ('IB/core: Display extended counter set if
>>>> available')
>>>>
>>>> Signed-off-by: Hal Rosenstock <hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>>> again, remove the blank line after the fixes tag.
>>>
>>> Also, I am not that the way Doug is setting the branch for pull would
>>> preserve commit IDs when
>>> the offending patch landed in Linus tree. If this is the case, we should
>>> put your patch in 2nd pull
>>> request and have the right commit ID there. Please check with Doug.
>>
>> Doug ?
>>
>
> The commit id should be preserved as long as the commit ID you reference
> is from my k.o tree and a k.o/ branch. It only changes if I rebase, and
> I don't do that on k.o branches that I've pushed to k.o (I have,
> however, once rebased a k.o/ branch that I had only pushed to
> github...and I try not to do that and will try even harder in the future
> not to, but I did do it once).
>
Oh, and I picked this up. Thanks.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2016-01-19 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 10:43 [PATCH v2] IB/core: sysfs.c: Fix PerfMgt ClassPortInfo handling Hal Rosenstock
[not found] ` <568263DF.6020505-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-12-29 12:21 ` Or Gerlitz
[not found] ` <56827AB7.50508-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-12-29 12:46 ` Hal Rosenstock
[not found] ` <568280BE.8030005-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2016-01-19 21:20 ` Doug Ledford
[not found] ` <569EA8B2.80607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-01-19 21:21 ` Doug Ledford [this message]
2015-12-29 16:58 ` Christoph Lameter
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=569EA8CA.3030304@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@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 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).