linux-kernel - Re: [PATCH 0/2] driver core: platform: Remove platform_device_add

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: <YKO1wiwCzSx62OIK@kroah.com>
Date:   Tue, 18 May 2021 14:40:34 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Thierry Reding <thierry.reding@...il.com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] driver core: platform: Remove
 platform_device_add_properties()

On Tue, May 18, 2021 at 02:48:37PM +0300, Andy Shevchenko wrote:
> On Tue, May 18, 2021 at 02:30:57PM +0300, Heikki Krogerus wrote:
> > On Tue, May 18, 2021 at 02:21:46PM +0300, Heikki Krogerus wrote:
> > > On Tue, May 18, 2021 at 11:59:22AM +0300, Andy Shevchenko wrote:
> > > > On Tue, May 18, 2021 at 11:30:44AM +0300, Heikki Krogerus wrote:
> > > > > Hi,
> > > > > 
> > > > > It looks like there is only one place left that still uses the
> > > > > function. Converting that last user and removing the thing.
> > > > > 
> > > > > Note, I'm actually resending the patch for board-paz00.c. I'm assuming
> > > > > the original patch slipped through the cracks because it did not end
> > > > > up anywhere.
> > > > 
> > > > Cool!
> > > > Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> > > > 
> > > > Btw, which base have you used for this series?
> > > 
> > > intel-next for this one.
> > 
> > I mean linux-next :-)
> 
> Let's wait for CIs to respond. I have a feeling that the first patch is good
> for v5.14, while the second one is probably for the next cycle.

Why?  I can take both now, no problem...