All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stephen Warren <swarren@nvidia.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: linux-next: build warning after merge of the mfd tree
Date: Sun, 7 Jul 2013 20:29:11 +0200	[thread overview]
Message-ID: <20130707182911.GA1799@breakpoint.cc> (raw)
In-Reply-To: <20130703155655.9fbacfa867af35fd743099e2@canb.auug.org.au>

On Wed, Jul 03, 2013 at 03:56:55PM +1000, Stephen Rothwell wrote:
> Hi Samuel,
Hi Stephen,

> Introduced by commit 18926edebcb8 ("iio: ti_am335x_adc: Allow to specify
> input line").  CONFIG_OF is not set in this build.
> 
> Maybe someone could come up with a way to make these arguments to
> of_property_for_each_u32() etc look used in the !CONFIG_OF case.

Already posted:

  https://lists.ozlabs.org/pipermail/devicetree-discuss/2013-June/035703.html

Sebastian

  reply	other threads:[~2013-07-07 18:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  5:56 linux-next: build warning after merge of the mfd tree Stephen Rothwell
2013-07-07 18:29 ` Sebastian Andrzej Siewior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-24  1:54 Stephen Rothwell
2025-07-24 10:03 ` Lee Jones
2025-07-29  1:35   ` Stephen Rothwell
2025-08-05  3:39     ` Stephen Rothwell
2025-08-05 13:19       ` Lee Jones
2020-07-07  2:44 Stephen Rothwell
     [not found] <20190627151140.232a87e2@canb.auug.org.au>
2019-06-27  5:59 ` Keerthy
2019-07-02  8:49   ` Stephen Rothwell
2019-07-02 11:09     ` Lee Jones
2018-06-05  3:15 Stephen Rothwell
2018-06-05  6:55 ` Lee Jones
2017-11-30  0:35 Stephen Rothwell
2017-11-30  8:28 ` Lee Jones
2017-01-25  4:54 Stephen Rothwell
2017-01-25  8:13 ` Benjamin Gaignard
2011-12-20  3:11 Stephen Rothwell
2010-11-29  0:52 Stephen Rothwell
2010-11-30 10:02 ` Samuel Ortiz
2010-03-03  5:22 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=20130707182911.GA1799@breakpoint.cc \
    --to=sebastian@breakpoint.cc \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=swarren@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 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.