From: Rob Herring <robh@kernel.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>, Al Stone <ahs3@redhat.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [PATCH v6 0/3] Preparation for further fwnode property cleanup
Date: Mon, 5 Jun 2017 10:12:24 -0500 [thread overview]
Message-ID: <CAL_JsqJtB-UVNLo3SM6apB-MODOSWwZzgeAE+ifsmT7U-5WJmw@mail.gmail.com> (raw)
In-Reply-To: <20170531122849.GG1019@valkosipuli.retiisi.org.uk>
On Wed, May 31, 2017 at 7:28 AM, Sakari Ailus <sakari.ailus@iki.fi> wrote:
> Hi Rob,
>
> On Wed, May 24, 2017 at 05:53:52PM +0300, Sakari Ailus wrote:
>> Hi Rob, Frank, others,
>>
>> Here's the 6th version of what used to be a single patch to prepare for
>> fwnode property cleanup.
>>
>> Beyond this, I have a couple of other patchsets I'll post in the near
>> future:
>>
>> - fwnode property cleanup (for linux-pm) which moves the property API
>> implementation to FW specific locations; depends on these patches,
>>
>> - V4L2 fwnode patches (for media_tree, no unmerged dependencies, pull
>> request sent) and
>>
>> - fwnode const patchset which allows making the fwnode argument for the
>> property API functions const. It depends on both of the previous sets.
>> Might be for linux-pm.
>
> I figured out that others are starting to have patches that depend on my
> other patchsets getting merged. Those patches are for the fwnode property
> API that most likely should go through the linux-pm tree as well as for the
> media tree.
>
> <URL:http://www.spinics.net/lists/linux-media/msg115893.html>
>
> I have hopes of being able to get the fwnode cleanup patchset (which the
> aforementioned patches depend on) in within this merge window --- assuming I
> could have your ack on the OF portions.
>
> Would it be possible to have an immutable branch for these or would you
> accept a pull request on v4.12-rc1?
I've applied this series. The stable branch is here:
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git dt/property-move
Rob
next prev parent reply other threads:[~2017-06-05 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 14:53 [PATCH v6 0/3] Preparation for further fwnode property cleanup Sakari Ailus
2017-05-24 14:53 ` [PATCH v6 1/3] of: Move OF property and graph API from base.c to property.c Sakari Ailus
2017-05-24 14:53 ` [PATCH v6 2/3] of: Make of_fwnode_handle() safer Sakari Ailus
2017-05-24 14:53 ` [PATCH v6 3/3] of: Support const and non-const use for to_of_node() Sakari Ailus
2017-05-31 12:28 ` [PATCH v6 0/3] Preparation for further fwnode property cleanup Sakari Ailus
2017-06-05 15:12 ` Rob Herring [this message]
2017-06-07 11:42 ` 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=CAL_JsqJtB-UVNLo3SM6apB-MODOSWwZzgeAE+ifsmT7U-5WJmw@mail.gmail.com \
--to=robh@kernel.org \
--cc=ahs3@redhat.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sudeep.holla@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.