From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robh@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"arm@kernel.org" <arm@kernel.org>,
Andy Gross <andy.gross@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the gpio tree
Date: Thu, 7 Dec 2017 16:10:21 +0100 [thread overview]
Message-ID: <CAK8P3a0s6+BsbxYLi5VejbBYuhhDRHPgWh5SM5i2KbJhVAY59Q@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqL2+ZRWdywRSNKLuWWJhvbYb6RHQKTWhJQWvZLABCy7TA@mail.gmail.com>
On Wed, Dec 6, 2017 at 9:51 PM, Rob Herring <robh@kernel.org> wrote:
> On Tue, Dec 5, 2017 at 4:48 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> These 2 aren't in -next and seem to have been missed:
>
> arm: dts: qcom: fix missing #phy-cells for apq8064
Apparently this is a subsect of 3191b5b332f8 ("ARM: dts: qcom-apq8064: Fix dsi
and hdmi phy cells"), which we already have
> arm: dts: nspire: Add missing #phy-cells to usb-nop-xceiv
Picked this one up now.
Arnd
next prev parent reply other threads:[~2017-12-07 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 5:37 linux-next: build warnings after merge of the gpio tree Stephen Rothwell
2017-11-09 3:51 ` Stephen Rothwell
2017-11-09 7:42 ` Linus Walleij
2017-11-09 14:37 ` Rob Herring
2017-11-15 22:42 ` Stephen Rothwell
2017-11-15 23:12 ` Rob Herring
2017-11-15 23:39 ` Stephen Rothwell
2017-12-05 22:48 ` Stephen Rothwell
2017-12-06 20:51 ` Rob Herring
2017-12-07 15:10 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-23 8:45 Stephen Rothwell
2014-07-23 8:46 ` Linus Walleij
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=CAK8P3a0s6+BsbxYLi5VejbBYuhhDRHPgWh5SM5i2KbJhVAY59Q@mail.gmail.com \
--to=arnd@arndb.de \
--cc=andy.gross@linaro.org \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).