From: Doug Ledford <dledford@redhat.com>
To: Salil Mehta <salil.mehta@huawei.com>, David Miller <davem@davemloft.net>
Cc: "Huwei (Xavier)" <xavier.huwei@huawei.com>,
oulijun <oulijun@huawei.com>,
"Zhuangyuzeng (Yisen)" <yisen.zhuang@huawei.com>,
"mehta.salil.lnk@gmail.com" <mehta.salil.lnk@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH for-next 0/2] {IB,net}/hns: Add support of ACPI to the Hisilicon RoCE Driver
Date: Thu, 25 Aug 2016 10:09:14 -0400 [thread overview]
Message-ID: <5d292cc1-5f1f-e0b0-0744-ac16ab4f14d5@redhat.com> (raw)
In-Reply-To: <F4CC6FACFEB3C54C9141D49AD221F7F91A6E813F@lhreml503-mbx>
[-- Attachment #1.1: Type: text/plain, Size: 3417 bytes --]
On 8/25/2016 8:08 AM, Salil Mehta wrote:
>
>
>> -----Original Message-----
>> From: Doug Ledford [mailto:dledford@redhat.com]
>> Sent: Thursday, August 25, 2016 12:57 PM
>> To: David Miller; Salil Mehta
>> Cc: Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen);
>> mehta.salil.lnk@gmail.com; linux-rdma@vger.kernel.org;
>> netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
>> Subject: Re: [PATCH for-next 0/2] {IB,net}/hns: Add support of ACPI to
>> the Hisilicon RoCE Driver
>>
>> On 8/25/2016 12:53 AM, David Miller wrote:
>>> From: Salil Mehta <salil.mehta@huawei.com>
>>> Date: Wed, 24 Aug 2016 04:44:48 +0800
>>>
>>>> This patch is meant to add support of ACPI to the Hisilicon RoCE
>> driver.
>>>> Following changes have been made in the driver(s):
>>>>
>>>> Patch 1/2: HNS Ethernet Driver: changes to support ACPI have been
>> done in
>>>> the RoCE reset function part of the HNS ethernet driver. Earlier
>> it only
>>>> supported DT/syscon.
>>>>
>>>> Patch 2/2. HNS RoCE driver: changes done in RoCE driver are meant to
>> detect
>>>> the type and then either use DT specific or ACPI spcific
>> functions. Where
>>>> ever possible, this patch tries to make use of "Unified Device
>> Property
>>>> Interface" APIs to support both DT and ACPI through single
>> interface.
>>>>
>>>> NOTE 1: ACPI changes done in both of the drivers depend upon the
>> ACPI Table
>>>> (DSDT and IORT tables) changes part of UEFI/BIOS. These changes
>> are NOT
>>>> part of this patch-set.
>>>> NOTE 2: Reset function in Patch 1/2 depends upon the reset function
>> added in
>>>> ACPI tables(basically DSDT table) part of the UEFI/BIOS. Again,
>> this
>>>> change is NOT reflected in this patch-set.
>>>
>>> I can't apply this series to my tree because the hns infiniband
>> driver
>>> doesn't exist in it.
>>>
>>
>> No. This probably needs to go through my tree. Although with all of
>> the requirements, I'm a bit concerned about those being present
>> elsewhere.
>>
>> --
>> Doug Ledford <dledford@redhat.com>
>> GPG Key ID: 0E572FDD
> Hello Doug,
> Thanks for your reply. I have just replied to David email as well and did
> not realize your response was already on the way. Sorry for this!
>
> I would just like to request, if by any chance, we can expedite the acceptance
> of the below patch (part of patch-set) in the net-next. This might help you as
> well in future when you will actually push the RoCE driver to the linux-next.
>
> "[PATCH for-next 1/2] net: hns: Add support of ACPI to HNS driver RoCE Reset
> function"
>
> Below HNS RoCE reset function patch has already been accepted by Dave Miller and
> is part of net-next,
> https://patchwork.kernel.org/patch/9287497/
>
> Also, above ACPI support of RoCE Reset patch cleanly applies over the already
> accepted patch in the link and is not dependent on other accompanying RoCE
> driver ACPI changes or even the presence of the Infiniband/RoCE Driver in the
> net-next repository.
>
> Could you please suggest if this the something which can be considered?
I've pulled both of these patches in. I usually merge late in the merge
window, so it won't be any stretch to wait until the ACPI tree has been
merged before I send Linus my pull request.
--
Doug Ledford <dledford@redhat.com>
GPG Key ID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2016-08-25 14:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 20:44 Salil Mehta
2016-08-23 20:44 ` [PATCH for-next 1/2] net: hns: Add support of ACPI to HNS driver RoCE Reset function Salil Mehta
2016-08-23 20:44 ` [PATCH for-next 2/2] IB/hns: Add support of ACPI to the Hisilicon RoCE driver Salil Mehta
2016-08-24 13:59 ` Leon Romanovsky
2016-08-24 14:25 ` Salil Mehta
2016-08-24 14:52 ` Leon Romanovsky
2016-08-25 4:53 ` [PATCH for-next 0/2] {IB,net}/hns: Add support of ACPI to the Hisilicon RoCE Driver David Miller
2016-08-25 11:57 ` Doug Ledford
2016-08-25 12:08 ` Salil Mehta
2016-08-25 14:09 ` Doug Ledford [this message]
2016-08-25 14:56 ` Salil Mehta
2016-09-05 12:53 ` Salil Mehta
2016-09-05 19:41 ` David Miller
2016-08-25 12:00 ` Salil Mehta
2016-08-25 13:52 ` Doug Ledford
2016-08-25 14:50 ` Salil Mehta
2016-08-25 15:00 ` Doug Ledford
2016-08-25 15:34 ` Salil Mehta
2016-09-05 10:13 ` Salil Mehta
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=5d292cc1-5f1f-e0b0-0744-ac16ab4f14d5@redhat.com \
--to=dledford@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mehta.salil.lnk@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oulijun@huawei.com \
--cc=salil.mehta@huawei.com \
--cc=xavier.huwei@huawei.com \
--cc=yisen.zhuang@huawei.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
all inboxes | Powered by JetHome®