linux-kernel - Re: [PATCH RESEND 2/2] ARM: da850: add the nand dev

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] [day] [month] [year] [list]

Message-ID: <ca65a02c-a067-9a4a-af7d-98bace48c5fd@ti.com>
Date:   Mon, 23 Jan 2017 21:29:15 +0530
From:   Sekhar Nori <nsekhar@...com>
To:     Bartosz Golaszewski <bgolaszewski@...libre.com>
CC:     Kevin Hilman <khilman@...libre.com>,
        Russell King <linux@...linux.org.uk>,
        Santosh Shilimkar <santosh.shilimkar@...cle.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        arm-soc <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH RESEND 2/2] ARM: da850: add the nand dev_id to the clock
 lookup table

On Monday 23 January 2017 09:02 PM, Bartosz Golaszewski wrote:
> 2017-01-23 16:17 GMT+01:00 Sekhar Nori <nsekhar@...com>:
>> On Friday 20 January 2017 07:16 PM, Sekhar Nori wrote:
>>> On Friday 13 January 2017 03:30 PM, Bartosz Golaszewski wrote:
>>>> The aemif driver can now access struct of_dev_auxdata (using platform
>>>> data).
>>>>
>>>> Add the device id to the clock lookup table for the nand clock and
>>>> create a separate lookup table for aemif subnodes.
>>>>
>>>> Signed-off-by: Bartosz Golaszewski <bgolaszewski@...libre.com>
>>>
>>> Applied to v4.11/soc
>>
>> I forgot that this has a build dependency with 1/2. Instead of creating
>> a dependency with Greg's tree, I think I will send it for v4.12. This is
>> a clean-up and does not add a new feature from a user's perspective so I
>> hope thats okay.
>>
>> Thanks,
>> Sekhar
> 
> Hi Sekhar,
> 
> Greg picked up both patches - 1/2 is already in char-misc-next[1].

Alright. I did not notice any merge conflicts between this and what I
plan to queue so I guess we are okay.

Thanks
Sekhar