From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH v1 1/1] device property: Don't split fwnode_get_irq*() APIs in the code
Date: Fri, 4 Feb 2022 10:32:27 +0200 [thread overview]
Message-ID: <Yfzkm1CVNNRqHzd7@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20220203125613.1166-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
On Thu, Feb 03, 2022 at 02:56:13PM +0200, Andy Shevchenko wrote:
> New fwnode_get_irq_byname() landed after an unrelated function
> by ordering. Move fwnode_iomap(), so fwnode_get_irq*() APIs will
> go together.
>
> No functional change intended.
I have no problem with the patch as such, but I have four patches moving
the implementation of this and other similar functions to OF and ACPI
frameworks. I moved what was here to OF/ACPI FWs as part of the fwnode
graph API implementation but some firmware type checks have crept back in
since that.
I'd prefer to prepend this patch to the rest of the set I have and get it
all merged through linux-pm tree, on the dependent patch reaches it.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2022-02-04 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 12:56 Andy Shevchenko
2022-02-04 8:32 ` Sakari Ailus [this message]
2022-02-04 9:41 ` Sakari Ailus
2022-02-04 13:40 ` Andy Shevchenko
2022-02-04 18:52 ` 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=Yfzkm1CVNNRqHzd7@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=wsa@kernel.org \
/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
all inboxes | Powered by JetHome®