linux-kernel - Re: [PATCH] i2c: xiic: Record xilinx i2c with Zynq fragment

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]

Date:   Fri, 7 Sep 2018 12:57:41 +0200
From:   Michal Simek <michal.simek@...inx.com>
To:     Wolfram Sang <wsa@...-dreams.de>,
        Michal Simek <michal.simek@...inx.com>
CC:     <linux-kernel@...r.kernel.org>, <monstr@...str.eu>,
        <linux-i2c@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Heiko Schocher <hs@...x.de>,
        Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
        <u-boot@...ts.denx.de>, Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] i2c: xiic: Record xilinx i2c with Zynq fragment

On 7.9.2018 12:34, Wolfram Sang wrote:
> On Fri, Sep 07, 2018 at 08:02:05AM +0200, Michal Simek wrote:
>> Include xilinx soft i2c controller to Zynq fragment to make clear who is
>> responsible for it.
>>
>> Signed-off-by: Michal Simek <michal.simek@...inx.com>
> 
> Cool, thanks!
> 
>> ---
>>
>> Normally we are handling all these drivers via one fragment to make sure
>> that there is only one central contact. Another reason is that people are
>> changing and their responsibility is moving time to time.
> 
> This is fine with me, but what about sorting the entries? I don't care
> much because it is "your" entry, yet I thought I mention it. Let me know
> if I should apply this as-is nonetheless.

It is not sorted even now that's why not big deal. I can sort it later
with this included.

Thanks,
Michal