linux-kernel - Re: [PATCH v5 0/3] i2c: Hookup typec power-negotation to the PMIC and charger

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, 20 Oct 2017 19:36:15 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Wolfram Sang <wsa@...-dreams.de>,
        Hans de Goede <hdegoede@...hat.com>
Cc:     Andy Shevchenko <andy.shevchenko@...il.com>,
        "Krogerus, Heikki" <heikki.krogerus@...ux.intel.com>,
        Darren Hart <dvhart@...radead.org>,
        Andy Shevchenko <andy@...radead.org>,
        Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-i2c <linux-i2c@...r.kernel.org>
Subject: Re: [PATCH v5 0/3] i2c: Hookup typec power-negotation to the PMIC
 and charger

On Thu, 2017-10-19 at 16:42 +0200, Wolfram Sang wrote:
> > The first patch, although it is an i2c-core change, is really
> > quite simple. I believe anyone can review it. But it does need
> > someone other then me to take a proper look (and not just do
> > a code only review) because it is a core change. Maybe there
> > is another way to solve the problem (persistent / predictable
> > device-names for i2c devices instantiated through board-data),
> > but I don't think so.
> 
> My plan is to hopefully meet Mark Brown (SPI and regulator maintainer)
> at ELCE next week and have a chat with him about this series.

If you don't mind I would like to join. (Yes, I will be at ELC next
week)

>  If all
> goes well, I'll merge it for v4.15.



-- 
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy