Re: [PATCH V2 for-next 0/8] Bug Fixes and Code Improvement in HNS driver

2016-10-13 Thread Doug Ledford 
On 10/13/2016 7:26 AM, Salil Mehta wrote:
>> -Original Message-
>> From: David Miller [mailto:da...@davemloft.net]
>> Sent: Friday, September 30, 2016 6:34 AM
>> To: Salil Mehta
>> Cc: dledf...@redhat.com; Zhuangyuzeng (Yisen); Huwei (Xavier); oulijun;
>> mehta.salil@gmail.com; linux-r...@vger.kernel.org;
>> netdev@vger.kernel.org; linux-ker...@vger.kernel.org; Linuxarm
>> Subject: Re: [PATCH V2 for-next 0/8] Bug Fixes and Code Improvement in
>> HNS driver
>>
>> From: Salil Mehta 
>> Date: Thu, 29 Sep 2016 18:09:08 +0100
>>
>>> This patch-set introduces fix to some Bugs, potential problems
>>> and code improvements identified during internal review and
>>> testing of Hisilicon Network Subsystem driver.
>>>
>>> Submit Change
>>> V1->V2: This addresses the feedbacks provided by David Miller
>>> and Doug Ledford
>>
>> So Doug my understanding is if this makes it through review
> Hi Dave,
> A gentle reminder regarding this. I was wondering if you think these
> have been reviewed enough and by any chance these patches can be included
> in current 4.9 merge window. This will save us a lot of effort.
> 
> As I understand Doug is waiting for your review approval on this
> patch-set.

I am, and I was just getting ready to ask again today myself.

> Thanks in anticipation
> Best regards
> Salil  
>> this is going to be merged into your tree, you prepare a
>> branch for me, and then I pull from that?
>>
>> Thanks in advance.


-- 
Doug Ledford 
GPG Key ID: 0E572FDD



signature.asc
Description: OpenPGP digital signature

RE: [PATCH V2 for-next 0/8] Bug Fixes and Code Improvement in HNS driver

2016-10-13 Thread Salil Mehta 
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Friday, September 30, 2016 6:34 AM
> To: Salil Mehta
> Cc: dledf...@redhat.com; Zhuangyuzeng (Yisen); Huwei (Xavier); oulijun;
> mehta.salil@gmail.com; linux-r...@vger.kernel.org;
> netdev@vger.kernel.org; linux-ker...@vger.kernel.org; Linuxarm
> Subject: Re: [PATCH V2 for-next 0/8] Bug Fixes and Code Improvement in
> HNS driver
> 
> From: Salil Mehta 
> Date: Thu, 29 Sep 2016 18:09:08 +0100
> 
> > This patch-set introduces fix to some Bugs, potential problems
> > and code improvements identified during internal review and
> > testing of Hisilicon Network Subsystem driver.
> >
> > Submit Change
> > V1->V2: This addresses the feedbacks provided by David Miller
> > and Doug Ledford
> 
> So Doug my understanding is if this makes it through review
Hi Dave,
A gentle reminder regarding this. I was wondering if you think these
have been reviewed enough and by any chance these patches can be included
in current 4.9 merge window. This will save us a lot of effort.

As I understand Doug is waiting for your review approval on this
patch-set.

Thanks in anticipation
Best regards
Salil  
> this is going to be merged into your tree, you prepare a
> branch for me, and then I pull from that?
> 
> Thanks in advance.

Re: [PATCH V2 for-next 0/8] Bug Fixes and Code Improvement in HNS driver

2016-09-30 Thread Doug Ledford 
On 9/30/16 1:33 AM, David Miller wrote:
> From: Salil Mehta 
> Date: Thu, 29 Sep 2016 18:09:08 +0100
> 
>> This patch-set introduces fix to some Bugs, potential problems
>> and code improvements identified during internal review and
>> testing of Hisilicon Network Subsystem driver.
>>
>> Submit Change
>> V1->V2: This addresses the feedbacks provided by David Miller
>> and Doug Ledford
> 
> So Doug my understanding is if this makes it through review
> this is going to be merged into your tree,

Correct.  Mainly because it sits on top of some other patches from Huawei.

> you prepare a
> branch for me, and then I pull from that?

I can.  It's either that or these 8 patches go to Linus through my tree.
 Be forewarned, the branch will have to include the entire hns-roce
driver and the hns/hns-roce ACPI reset support patches.  That may be
more than you intended to get in a pull.  But it's a kind of messed up
branch anyway.  I couldn't submit the branch until after you submit your
pull request to Linus because the branch itself is based on an older
version of your net-next tree, which was needed to get the hns-roce
driver to go in cleanly. I just added the hns-roce stuff on top of that.
 My original intent, because of all this, was that this branch would be
submitted as its own special pull request once most other stuff was
already in.

> Thanks in advance.

Sure.

-- 
Doug Ledford GPG Key ID: 0E572FDD
  Red Hat, Inc.
  100 E. Davie St
  Raleigh, NC 27601 USA



signature.asc
Description: OpenPGP digital signature

Re: [PATCH V2 for-next 0/8] Bug Fixes and Code Improvement in HNS driver

2016-09-29 Thread David Miller 
From: Salil Mehta 
Date: Thu, 29 Sep 2016 18:09:08 +0100

> This patch-set introduces fix to some Bugs, potential problems
> and code improvements identified during internal review and
> testing of Hisilicon Network Subsystem driver.
> 
> Submit Change
> V1->V2: This addresses the feedbacks provided by David Miller
> and Doug Ledford

So Doug my understanding is if this makes it through review
this is going to be merged into your tree, you prepare a
branch for me, and then I pull from that?

Thanks in advance.