From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH RESEND 0/2] driver core: platform: Remove platform_device_add_properties()
Date: Tue, 17 Aug 2021 13:24:47 +0300 [thread overview]
Message-ID: <20210817102449.39994-1-heikki.krogerus@linux.intel.com> (raw)
Hi,
It seems Rafael never took these. Let's try again.
The original cover letter:
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.
I would imagine that it's OK to everybody if Greg takes these?
thanks,
Heikki Krogerus (2):
ARM: tegra: paz00: Handle device properties with software node API
driver core: platform: Remove platform_device_add_properties()
arch/arm/mach-tegra/board-paz00.c | 2 +-
drivers/base/platform.c | 20 ++------------------
include/linux/platform_device.h | 2 --
3 files changed, 3 insertions(+), 21 deletions(-)
--
2.30.2
next reply other threads:[~2021-08-17 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 10:24 Heikki Krogerus [this message]
2021-08-17 10:24 ` [PATCH RESEND 1/2] ARM: tegra: paz00: Handle device properties with software node API Heikki Krogerus
2021-08-17 14:30 ` Thierry Reding
2021-08-18 10:57 ` Greg Kroah-Hartman
2021-08-17 10:24 ` [PATCH RESEND 2/2] driver core: platform: Remove platform_device_add_properties() Heikki Krogerus
2021-08-17 14:32 ` Thierry Reding
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=20210817102449.39994-1-heikki.krogerus@linux.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).