From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
Arun Murthy <arun.murthy@stericsson.com>,
linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: Make AB8500_PWM driver depend on U8500 due to PWM breakage
Date: Mon, 20 Dec 2010 14:00:05 +0100 [thread overview]
Message-ID: <20101220130004.GG11095@sortiz-mobl> (raw)
In-Reply-To: <1292848091-29959-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Mon, Dec 20, 2010 at 12:28:11PM +0000, Mark Brown wrote:
> Since we don't have a PWM API every PWM driver ends up exporting its
> own version and we need to limit the platforms we try to build them on
> in order to avoid multiple definitions. As the AB8500 is normally a
> companion chip for the U8500 CPU depend on that architecture.
>
> Previously the driver was relying on the AB8500 core only being built
> on U8500 but this did not give us build coverage of any of the other
> functions for the device.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>
> Here's a better way of solving the problem,
Definitely nicer, yes. Patch applied, thanks a lot.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2010-12-20 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 8:21 linux-next: build failure after merge of the final tree (mfd tree related) Stephen Rothwell
2010-12-20 10:33 ` Samuel Ortiz
2010-12-20 10:52 ` Mark Brown
2010-12-20 12:18 ` Mark Brown
2010-12-20 12:28 ` [PATCH] misc: Make AB8500_PWM driver depend on U8500 due to PWM breakage Mark Brown
2010-12-20 13:00 ` Samuel Ortiz [this message]
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=20101220130004.GG11095@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=arun.murthy@stericsson.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linus.walleij@stericsson.com \
--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 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.