linux-kernel - Re: [PATCH 0/3] Add driver for Synopsys DesignWare I3C master IP

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: <20180721191515.6b20d23b@bbrezillon>
Date:   Sat, 21 Jul 2018 19:15:15 +0200
From:   Boris Brezillon <boris.brezillon@...tlin.com>
To:     Wolfram Sang <wsa@...-dreams.de>
Cc:     Vitor soares <Vitor.Soares@...opsys.com>,
        linux-i2c@...r.kernel.org, corbet@....net,
        linux-doc@...r.kernel.org, gregkh@...uxfoundation.org,
        arnd@...db.de, psroka@...ence.com, agolec@...ence.com,
        adouglas@...ence.com, bfolta@...ence.com, dkos@...ence.com,
        alicja@...ence.com, cwronka@...ence.com, sureshp@...ence.com,
        rafalc@...ence.com, thomas.petazzoni@...tlin.com, nm@...com,
        robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
        ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        geert@...ux-m68k.org, linus.walleij@...aro.org,
        Xiang.Lin@...aptics.com, linux-gpio@...r.kernel.org,
        nsekhar@...com, pgaj@...ence.com, peda@...ntia.se,
        Joao.Pinto@...opsys.com
Subject: Re: [PATCH 0/3] Add driver for Synopsys DesignWare I3C master IP

Hi Wolfram,

On Fri, 20 Jul 2018 23:58:01 +0200
Wolfram Sang <wsa@...-dreams.de> wrote:

> On Fri, Jul 20, 2018 at 09:57:49PM +0100, Vitor soares wrote:
> > This patch series is a proposal for the I3C master driver for Synopsys IP.
> > This patch is to be applied on top of I3C subsystem RFC V6 submitted
> > by Boris Brezillon.  
> 
> Nice! More users will help the subsystem evolve.
> 
> Yet, I also think this may be a good timing for a seperate I3C mailing
> list? We can always cross-post if I2C is relevant, but I guess new I3C
> masters usually are very I3C specific. I think a seperate mailing list
> would also look good in the MAINTAINERS entry.
> 

I was waiting for the I3C framework to be merged before creating the ML
and the git repo, but if you think we should do that now I can create
them.

Regards,

Boris