From: Frank Rowand <frowand.list@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Rob Herring <robh+dt@kernel.org>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/4] of: remove *phandle properties from expanded device tree
Date: Wed, 21 Jun 2017 12:25:44 -0700 [thread overview]
Message-ID: <594AC838.5010901@gmail.com> (raw)
In-Reply-To: <594A0FB6.2000102@gmail.com>
On 06/20/17 23:18, Frank Rowand wrote:
> Hi Rob,
>
> Michael has an issue that means this patch series is not OK in the
> current form. I will work on a v7 to see if I can resolve the
> issue.
>
> -Frank
< snip >
Hi Rob,
The issue is in patch 1. Patches 2 - 4 are small independent patches
that are not dependent on patch 1, so I just sent them as individual
patches. Version 7 of this series will be just patch 1.
-Frank
next prev parent reply other threads:[~2017-06-21 19:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 22:02 [PATCH v6 0/4] of: remove *phandle properties from expanded device tree frowand.list
2017-06-20 22:02 ` frowand.list-Re5JQEeQqe8AvxtiuMwx3w
2017-06-20 22:02 ` [PATCH v6 1/4] " frowand.list
2017-06-21 4:57 ` Michael Ellerman
2017-06-21 4:57 ` Michael Ellerman
2017-06-21 4:57 ` Michael Ellerman
2017-06-21 6:18 ` Frank Rowand
2017-06-21 19:25 ` Frank Rowand [this message]
2017-06-21 23:56 ` Frank Rowand
2017-06-21 23:56 ` Frank Rowand
2017-06-22 15:54 ` Rob Herring
2017-08-02 18:16 ` Frank Rowand
2017-06-20 22:02 ` [PATCH v6 2/4] of: make __of_attach_node() static frowand.list
2017-06-21 23:46 ` Stephen Boyd
2017-06-21 23:46 ` Stephen Boyd
2017-06-20 22:02 ` [PATCH v6 3/4] of: be consistent in form of file mode frowand.list
2017-06-20 22:02 ` frowand.list-Re5JQEeQqe8AvxtiuMwx3w
2017-06-20 22:02 ` [PATCH v6 4/4] of: detect invalid phandle in overlay frowand.list
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=594AC838.5010901@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nfont@linux.vnet.ibm.com \
--cc=robh+dt@kernel.org \
--cc=tyreld@linux.vnet.ibm.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.