From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Thierry Reding <treding@nvidia.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 27
Date: Wed, 27 Apr 2016 16:31:36 +0900 [thread overview]
Message-ID: <20160427073136.GB7601@swordfish> (raw)
In-Reply-To: <20160427170354.5c643779@canb.auug.org.au>
Hello,
commit 2f7600bc981cb0fd7ea0b92618bae32dcc778317
Author: Thierry Reding <treding@nvidia.com>
Date: Tue Apr 5 17:17:34 2016 +0200
phy: core: Allow children node to be overridden
In order to more flexibly support device tree bindings, allow drivers to
override the container of the child nodes. By default the device node of
the PHY provider is assumed to be the parent for children, but bindings
may decide to add additional levels for better organization.
this does not compile on !CONFIG_OF systems
drivers/phy/phy-core.c: In function ‘__of_phy_provider_register’:
drivers/phy/phy-core.c:848:13: error: implicit declaration of function ‘of_get_next_parent’ [-Werror=implicit-function-declaration]
parent = of_get_next_parent(parent);
^~~~~~~~~~~~~~~~~~
drivers/phy/phy-core.c:848:11: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
parent = of_get_next_parent(parent);
^
CC [M] drivers/net/usb/usbnet.o
cc1: some warnings being treated as errors
CC net/ipv4/proc.o
scripts/Makefile.build:289: recipe for target 'drivers/phy/phy-core.o' failed
make[2]: *** [drivers/phy/phy-core.o] Error 1
scripts/Makefile.build:440: recipe for target 'drivers/phy' failed
make[1]: *** [drivers/phy] Error 2
make[1]: *** Waiting for unfinished jobs....
-ss
next prev parent reply other threads:[~2016-04-27 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 7:03 linux-next: Tree for Apr 27 Stephen Rothwell
2016-04-27 7:08 ` Stephen Rothwell
2016-04-27 7:31 ` Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-27 15:08 broonie
2022-04-27 6:23 Stephen Rothwell
2021-04-27 7:40 Stephen Rothwell
2017-04-27 6:39 Stephen Rothwell
2015-04-27 2:17 Stephen Rothwell
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=20160427073136.GB7601@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).