From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Xiubo Li <Li.Xiubo@freescale.com>
Subject: Re: linux-next: build failure after merge of the devicetree tree
Date: Mon, 26 May 2014 09:22:37 +0200 [thread overview]
Message-ID: <20140526092237.24631389@free-electrons.com> (raw)
In-Reply-To: <20140526150557.219ea08f@canb.auug.org.au>
Dear Stephen Rothwell,
On Mon, 26 May 2014 15:05:57 +1000, Stephen Rothwell wrote:
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 395ee2b3146d..03e7fc6c93e8 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -1901,10 +1901,6 @@ int of_update_property(struct device_node *np, struct property *newprop)
> if (!of_kset)
> return 0;
>
> - /* At early boot, bail out and defer setup to of_init() */
> - if (!of_kset)
> - return found ? 0 : -ENODEV;
> -
Seems like this is in fact reverting my change entirely, so maybe Grant
should drop my patch instead?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-26 7:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 5:05 linux-next: build failure after merge of the devicetree tree Stephen Rothwell
2014-05-26 7:22 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-17 4:13 Stephen Rothwell
2023-12-11 5:05 Stephen Rothwell
2023-12-12 9:04 ` Sibi Sankar
2024-01-19 0:58 ` Stephen Rothwell
2024-01-19 14:07 ` Rob Herring
2023-12-08 2:51 Stephen Rothwell
2023-12-08 7:34 ` Krzysztof Kozlowski
2023-12-07 1:57 Stephen Rothwell
2023-12-07 15:11 ` Rob Herring
2023-12-07 20:58 ` Stephen Rothwell
2023-12-07 22:05 ` Rob Herring
2023-12-08 3:11 ` Stephen Rothwell
2023-04-11 2:28 Stephen Rothwell
2011-10-05 5:24 Stephen Rothwell
2011-10-05 5:54 ` Grant Likely
2010-07-30 3:57 Stephen Rothwell
2010-07-30 6:11 ` Grant Likely
2010-07-15 2:15 Stephen Rothwell
2010-07-15 6:06 ` Grant Likely
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=20140526092237.24631389@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=Li.Xiubo@freescale.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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