From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] driver core: platform: Remove platform_device_add_properties()
Date: Tue, 18 May 2021 17:26:26 +0200 [thread overview]
Message-ID: <YKPcol2IUVDHMGTE@kroah.com> (raw)
In-Reply-To: <CAJZ5v0hyXOQuLCKB9D_-j64VK-syo5AZmSgEGRHSyuMyvVciOg@mail.gmail.com>
On Tue, May 18, 2021 at 02:53:09PM +0200, Rafael J. Wysocki wrote:
> On Tue, May 18, 2021 at 2:40 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > 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@linux.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...
>
> Not really, there are dependencies, one in my tree ATM.
>
> It's better if I take them IMHO.
Sure, feel free to:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2021-05-18 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 8:30 [PATCH 0/2] driver core: platform: Remove platform_device_add_properties() Heikki Krogerus
2021-05-18 8:30 ` [PATCH 1/2] ARM: tegra: paz00: Handle device properties with software node API Heikki Krogerus
2021-05-18 8:30 ` [PATCH 2/2] driver core: platform: Remove platform_device_add_properties() Heikki Krogerus
2021-05-18 8:59 ` [PATCH 0/2] " Andy Shevchenko
2021-05-18 11:21 ` Heikki Krogerus
2021-05-18 11:30 ` Heikki Krogerus
2021-05-18 11:48 ` Andy Shevchenko
2021-05-18 12:40 ` Greg Kroah-Hartman
2021-05-18 12:53 ` Rafael J. Wysocki
2021-05-18 15:26 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YKPcol2IUVDHMGTE@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.