linux-kernel - Re: [PATCH v11 0/3]add PCIe driver for Kirin PCIe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFGCpxy-Rn4aeRs6GwGu7kaXvk5ftQxSpho8D2kQ4OG5MgCA8w@mail.gmail.com>
Date:   Tue, 4 Jul 2017 10:03:08 +0800
From:   Guodong Xu <guodong.xu@...aro.org>
To:     Wei Xu <xuwei5@...ilicon.com>
Cc:     Bjorn Helgaas <helgaas@...nel.org>,
        Xiaowei Song <songxiaowei@...ilicon.com>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Rob Herring <robh+dt@...nel.org>,
        Suzhuangluan <suzhuangluan@...ilicon.com>,
        linux-pci <linux-pci@...r.kernel.org>,
        devicetree@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Catalin Marinas <catalin.marinas@....com>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Will Deacon <will.deacon@....com>
Subject: Re: [PATCH v11 0/3]add PCIe driver for Kirin PCIe

On Mon, Jul 3, 2017 at 9:32 PM, Wei Xu <xuwei5@...ilicon.com> wrote:
> Hi Guodong,
>
> On 2017/7/3 14:04, Guodong Xu wrote:
>> Hi, Xu Wei
>>
>>
>>
>> On Mon, Jul 3, 2017 at 6:47 PM, Will Deacon <will.deacon@....com> wrote:
>>> On Sun, Jul 02, 2017 at 06:36:57PM -0500, Bjorn Helgaas wrote:
>>>> [+cc Catalin, Will, linux-arm-kernel]
>>>>
>>>> Applied patches 2 & 3 to pci/host-kirin for v4.13.
>>>>
>>>> I would like a MAINTAINERS update, too.  If you send me that, I'll
>>>> squash it into the driver patch.
>>>>
>>>> Catalin, Will, how do you want to handle the
>>>> arch/arm64/configs/defconfig change (patch 3)?  It's currently on my
>>>> branch, but I'm happy to drop it if another route is better.
>>>
>>> defconfig updates usually go through arm-soc, via the relevant platform
>>> maintainer, so it would be best to follow that route here too otherwise
>>> you'll probably see conflicts in -next.
>>>
>>
>> Is it ok for you to pick up the arch/arm64/configs/defconfig change (patch 3)?
>
> Since it is already 4.12-rc7, I will pick up it and queue for the v4.14.
> Are you fine about that?
> Thanks!

Sure.

>
> Best Regards,
> Wei
>
>>
>> -Guodong
>>
>>> Will
>>
>> .
>>
>