public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Scally <djrscally@gmail.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH 0/4] Shovel firmware specific code to appropriate locations
Date: Mon, 7 Feb 2022 14:27:43 +0200	[thread overview]
Message-ID: <YgEQP3QGtqre+nCL@smile.fi.intel.com> (raw)
In-Reply-To: <20220206091643.276833-1-sakari.ailus@linux.intel.com>

On Sun, Feb 06, 2022 at 11:16:39AM +0200, Sakari Ailus wrote:
> Hi folks,
> 
> This set moves the implementation of recently added device property API
> functions to OF and ACPI frameworks, where the rest of such functionality
> resides.
> 
> Compile tested.

All look good to me,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

> Note that after some initial confusion, this set actually does depend on
> Andy's patch "device property: Don't split fwnode_get_irq*() APIs in the
> code" to appear in the linux-acpi tree.

Perhaps than you can add to your series the conversion of
fwnode_irq_get_byname()?

> Sakari Ailus (4):
>   device property: Convert device_{dma_supported,get_dma_attr} to fwnode
>   ACPI: property: Move acpi_fwnode_device_get_match_data() up
>   device property: Add iomap to fwnode operations
>   device property: Add irq_get to fwnode operation
> 
>  drivers/acpi/property.c | 36 +++++++++++++++++++++++++++++++----
>  drivers/base/property.c | 42 ++++++-----------------------------------
>  drivers/of/property.c   | 31 ++++++++++++++++++++++++++++++
>  include/linux/fwnode.h  |  5 +++++
>  4 files changed, 74 insertions(+), 40 deletions(-)
> 
> -- 
> 2.30.2
> 
> 

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2022-02-07 13:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06  9:16 [PATCH 0/4] Shovel firmware specific code to appropriate locations Sakari Ailus
2022-02-06  9:16 ` [PATCH 1/4] device property: Convert device_{dma_supported,get_dma_attr} to fwnode Sakari Ailus
2022-02-07 12:20   ` Andy Shevchenko
2022-02-11 15:55   ` Rob Herring
2022-02-11 16:18     ` Andy Shevchenko
2022-03-08 15:50       ` Rob Herring
2022-02-14 13:31     ` Sakari Ailus
2022-02-06  9:16 ` [PATCH 2/4] ACPI: property: Move acpi_fwnode_device_get_match_data() up Sakari Ailus
2022-02-06  9:16 ` [PATCH 3/4] device property: Add iomap to fwnode operations Sakari Ailus
2022-02-11 15:59   ` Rob Herring
2022-02-14 10:31     ` Sakari Ailus
2022-02-06  9:16 ` [PATCH 4/4] device property: Add irq_get to fwnode operation Sakari Ailus
2022-02-11 16:02   ` Rob Herring
2022-02-07 12:27 ` Andy Shevchenko [this message]
2022-02-07 14:41   ` [PATCH 0/4] Shovel firmware specific code to appropriate locations Sakari Ailus

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=YgEQP3QGtqre+nCL@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=djrscally@gmail.com \
    --cc=frowand.list@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh+dt@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