From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sasha Levin <levinsasha928@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 18:05:26 +0300 [thread overview]
Message-ID: <4FAD2AB6.7030403@ti.com> (raw)
In-Reply-To: <4FAD1C38.5050907@windriver.com>
Hi,
On 05/11/2012 05:03 PM, Paul Gortmaker wrote:
> Hi Dmitry,
>
> It should be limited to the platforms where the hardware is available,
> so that coverage builds aren't needlessly spending cycles building
> stuff that can't possibly ever be used. Also if it is limited to
> ARM, then we can't have an ARM bug like this one mask the x86_64
> allyesconfig build from uncovering possible errors that we really
> care about seeing.
The cleanest way to do this is to make the twl6040 MFD
(CONFIG_TWL6040_CORE) to depend on ARM (or on OMAP). That way none of
the drivers depending on it will got built on non ARM platforms.
--
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: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sasha Levin <levinsasha928@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 18:05:26 +0300 [thread overview]
Message-ID: <4FAD2AB6.7030403@ti.com> (raw)
In-Reply-To: <4FAD1C38.5050907@windriver.com>
Hi,
On 05/11/2012 05:03 PM, Paul Gortmaker wrote:
> Hi Dmitry,
>
> It should be limited to the platforms where the hardware is available,
> so that coverage builds aren't needlessly spending cycles building
> stuff that can't possibly ever be used. Also if it is limited to
> ARM, then we can't have an ARM bug like this one mask the x86_64
> allyesconfig build from uncovering possible errors that we really
> care about seeing.
The cleanest way to do this is to make the twl6040 MFD
(CONFIG_TWL6040_CORE) to depend on ARM (or on OMAP). That way none of
the drivers depending on it will got built on non ARM platforms.
--
Péter
next prev parent reply other threads:[~2012-05-11 15:05 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
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 [this message]
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=4FAD2AB6.7030403@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.