From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Len Brown <lenb@kernel.org>
Subject: [PATCH v2 0/4] driver core & device property: clean up APIs
Date: Fri, 23 Feb 2024 17:54:35 +0200 [thread overview]
Message-ID: <20240223155731.858412-1-andriy.shevchenko@linux.intel.com> (raw)
There are two, but dependent pair of patches that:
- hides unused devlink APIs
- removes 'proxy' header use
v2:
- most of the patches were sent separately as v1, thus this series is v2
- harvested tags from that patches (Sakari, Saravana)
Andy Shevchenko (4):
driver core: Drop unneeded 'extern' keyword in fwnode.h
driver core: Move fw_devlink stuff to where it belongs
device property: Move enum dev_dma_attr to fwnode.h
device property: Don't use "proxy" headers
drivers/base/core.c | 58 ++++++++++++++++++++++++++++++++++
drivers/base/property.c | 67 ++++------------------------------------
drivers/base/swnode.c | 13 +++++++-
include/linux/fwnode.h | 13 +++++---
include/linux/property.h | 9 +-----
5 files changed, 86 insertions(+), 74 deletions(-)
--
2.43.0.rc1.1.gbec44491f096
next reply other threads:[~2024-02-23 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 15:54 Andy Shevchenko [this message]
2024-02-23 15:54 ` [PATCH v2 1/4] driver core: Drop unneeded 'extern' keyword in fwnode.h Andy Shevchenko
2024-02-23 15:54 ` [PATCH v2 2/4] driver core: Move fw_devlink stuff to where it belongs Andy Shevchenko
2024-02-28 21:14 ` Rafael J. Wysocki
2024-02-23 15:54 ` [PATCH v2 3/4] device property: Move enum dev_dma_attr to fwnode.h Andy Shevchenko
2024-02-23 15:54 ` [PATCH v2 4/4] device property: Don't use "proxy" headers Andy Shevchenko
2024-02-28 21:01 ` [PATCH v2 0/4] driver core & device property: clean up APIs Rafael J. Wysocki
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=20240223155731.858412-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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