From: Grant Likely <grant.likely@linaro.org>
To: Nathan Fontenot <nfont@austin.ibm.com>,
linux-kernel@vger.kernel.org,
Tyrel Datwyler <turtle.in.the.kernel@gmail.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 00/10] of: Core devicetree changeset support
Date: Sun, 27 Jul 2014 08:43:31 -0600 [thread overview]
Message-ID: <20140727144331.73789C40603@trevor.secretlab.ca> (raw)
In-Reply-To: <53D29D87.4060708@austin.ibm.com>
On Fri, 25 Jul 2014 13:10:15 -0500, Nathan Fontenot <nfont@austin.ibm.com> wrote:
> On 07/23/2014 06:44 PM, Grant Likely wrote:
> > Hi all,
> >
> > This is a rollup of all the patches that I queued up today for
> > linux-next for the devicetree changeset and overlay work. I'm reposting
> > these patches because some have been significantly changed since their
> > first posting. None of the code is actually live yet, but the test cases
> > are there.
> >
> > There is one significant functional change which may affect pseries. The
> > OF_DYNAMIC code has been changed to emit notifiers after applying a
> > change to the tree instead of before. I think I've got all they users
> > taken care of correctly, but I'd like to see some testing. I don't have
> > access to pseries (and I can't get the QEMU pseries model to boot reliably)
> >
> > Nathan/Tyrel, can you give it a spin? The changes can be found in my git tree:
>
> Grant,
>
> I was able to do some sniff testing by adding/removing memory, cpus, and pci
> devices and it appears that all device tree nodes and properties were updated
> properly.
>
> I would still like to try doing live partition migration where we can update
> many pieces of the device tree. I'll be out next week, will try to get
> on that when I return.
Thanks Nathan,
In the mean time, all this stuff is in Linux next. I would really like
to merge it for v3.17. I expect the merge window will open next weekend.
Let me know once you've been able to do the migration test. I can hold
off sending Linus a pull request until wk2 of the merge window if you
need the extra time.
g.
prev parent reply other threads:[~2014-07-27 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 23:44 Grant Likely
2014-07-23 23:44 ` [PATCH 01/10] of/platform: Fix of_platform_device_destroy iteration of devices Grant Likely
2014-07-23 23:44 ` [PATCH 02/10] of: rename of_aliases_mutex to just of_mutex Grant Likely
2014-07-23 23:44 ` [PATCH 03/10] of: Move CONFIG_OF_DYNAMIC code into a separate file Grant Likely
2014-07-23 23:44 ` [PATCH 04/10] OF: Utility helper functions for dynamic nodes Grant Likely
2014-07-23 23:44 ` [PATCH 05/10] of: Create unlocked versions of node and property add/remove functions Grant Likely
2014-07-23 23:44 ` [PATCH 06/10] of: Make devicetree sysfs update functions consistent Grant Likely
2014-07-23 23:44 ` [PATCH 07/10] of: Make sure attached nodes don't carry along extra children Grant Likely
2014-07-23 23:44 ` [PATCH 08/10] of: Move dynamic node fixups out of powerpc and into common code Grant Likely
2014-07-23 23:44 ` [PATCH 09/10] of: Reorder device tree changes and notifiers Grant Likely
2014-07-23 23:44 ` [PATCH 10/10] of: Transactional DT support Grant Likely
2014-07-25 18:10 ` [PATCH 00/10] of: Core devicetree changeset support Nathan Fontenot
2014-07-27 14:43 ` Grant Likely [this message]
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=20140727144331.73789C40603@trevor.secretlab.ca \
--to=grant.likely@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfont@austin.ibm.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=turtle.in.the.kernel@gmail.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
all inboxes | Powered by JetHome®