All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
	dmitry.torokhov@gmail.com, broonie@opensource.wolfsonicro.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] TWL6040: fix build error
Date: Fri, 11 May 2012 10:03:51 +0300	[thread overview]
Message-ID: <4FACB9D7.5090100@ti.com> (raw)
In-Reply-To: <CAP=VYLqwAO8x4aWw7_pH1LH_SPO9Td2ec9oOmKPL-_5LOEQw3g@mail.gmail.com>

Hi,

On 05/11/2012 01:49 AM, Paul Gortmaker wrote:
> On Thu, May 10, 2012 at 2:44 PM, Sasha Levin <levinsasha928@gmail.com> wrote:
>> Fixes build error due to missing of_property_read_u32.
> 
> Yes, I saw the same on x86-64 allyesconfig -- which means that in addition to
> this missing header, it needs to have a Kconfig dependency that limits
> it to just being enabled on the platforms where it physically is possible to
> have the hardware.  I'm guessing limiting to ARM would be a good start?

Yes it is only usable on ARM, most specifically on OMAP4+ platforms.
If I make the twl6040 MFD core to depend on ARM (or even on OMAP) this
won't happen again.


-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
	dmitry.torokhov@gmail.com, broonie@opensource.wolfsonicro.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] TWL6040: fix build error
Date: Fri, 11 May 2012 10:03:51 +0300	[thread overview]
Message-ID: <4FACB9D7.5090100@ti.com> (raw)
In-Reply-To: <CAP=VYLqwAO8x4aWw7_pH1LH_SPO9Td2ec9oOmKPL-_5LOEQw3g@mail.gmail.com>

Hi,

On 05/11/2012 01:49 AM, Paul Gortmaker wrote:
> On Thu, May 10, 2012 at 2:44 PM, Sasha Levin <levinsasha928@gmail.com> wrote:
>> Fixes build error due to missing of_property_read_u32.
> 
> Yes, I saw the same on x86-64 allyesconfig -- which means that in addition to
> this missing header, it needs to have a Kconfig dependency that limits
> it to just being enabled on the platforms where it physically is possible to
> have the hardware.  I'm guessing limiting to ARM would be a good start?

Yes it is only usable on ARM, most specifically on OMAP4+ platforms.
If I make the twl6040 MFD core to depend on ARM (or even on OMAP) this
won't happen again.


-- 
Péter

  parent reply	other threads:[~2012-05-11  7:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 18:44 [PATCH] TWL6040: fix build error Sasha Levin
2012-05-10 22:49 ` Paul Gortmaker
2012-05-10 22:49   ` Paul Gortmaker
2012-05-11  2:50   ` Sasha Levin
2012-05-11  2:50     ` Sasha Levin
2012-05-11  2:58     ` Paul Gortmaker
2012-05-11  2:58       ` Paul Gortmaker
2012-05-11  4:27   ` Grant Likely
2012-05-11  4:27     ` Grant Likely
2012-05-11 12:16     ` Peter Ujfalusi
2012-05-11 12:16       ` Peter Ujfalusi
2012-05-11  7:03   ` Peter Ujfalusi [this message]
2012-05-11  7:03     ` Peter Ujfalusi
2012-05-11  7:20     ` Dmitry Torokhov
2012-05-11 14:03       ` Paul Gortmaker
2012-05-11 14:03         ` Paul Gortmaker
2012-05-11 15:05         ` Peter Ujfalusi
2012-05-11 15:05           ` Peter Ujfalusi
2012-05-11 15:49         ` Dmitry Torokhov
2012-05-11 16:10           ` Paul Gortmaker
2012-05-11 16:10             ` Paul Gortmaker
2012-05-13 10:53   ` Mark Brown
2012-05-11  4:03 ` Dmitry Torokhov
2012-05-11  6:58 ` Peter Ujfalusi

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=4FACB9D7.5090100@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=broonie@opensource.wolfsonicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.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.