From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Len Brown <lenb@kernel.org>, Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v3 0/4] driver core & device property: clean up APIs
Date: Thu, 29 Feb 2024 19:46:15 +0100 [thread overview]
Message-ID: <2024022958-motocross-abdominal-e709@gregkh> (raw)
In-Reply-To: <20240229162741.3854912-1-andriy.shevchenko@linux.intel.com>
On Thu, Feb 29, 2024 at 06:23:42PM +0200, Andy Shevchenko wrote:
> There are two, but dependent pair of patches that:
> - makes some of devlink APIs static
> - removes 'proxy' header use
>
> This is rebased on top of latest patches from Jonathan as it has a minor
> conflict in property.h. The series can be applied directly to driver
> core tree with reduced context, but it may be better just to route it
> via IIO. Greg, which way do you prefer?
Why would IIO mess with driver core stuff?
I can just take it in my driver core tree, thanks.
greg k-h
next prev parent reply other threads:[~2024-02-29 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 16:23 [PATCH v3 0/4] driver core & device property: clean up APIs Andy Shevchenko
2024-02-29 16:23 ` [PATCH v3 1/4] driver core: Drop unneeded 'extern' keyword in fwnode.h Andy Shevchenko
2024-02-29 16:23 ` [PATCH v3 2/4] driver core: Move fw_devlink stuff to where it belongs Andy Shevchenko
2024-02-29 16:23 ` [PATCH v3 3/4] device property: Move enum dev_dma_attr to fwnode.h Andy Shevchenko
2024-02-29 16:23 ` [PATCH v3 4/4] device property: Don't use "proxy" headers Andy Shevchenko
2024-02-29 18:46 ` Greg Kroah-Hartman [this message]
2024-03-01 17:57 ` [PATCH v3 0/4] driver core & device property: clean up APIs Andy Shevchenko
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=2024022958-motocross-abdominal-e709@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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