From: Arnd Bergmann <arnd.bergmann@linaro.org>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: linux-next: build failure after merge of the final tree (pwm tree related)
Date: Sat, 30 Jun 2012 20:12:32 +0000 [thread overview]
Message-ID: <201206302012.32476.arnd.bergmann@linaro.org> (raw)
In-Reply-To: <20120630194139.GA24300@avionic-0098.mockup.avionic-design.de>
On Saturday 30 June 2012, Thierry Reding wrote:
> > I think that all the drivers that are not converted to the common PWM
> > layer yet should depend on not enabling the common code. Once they
> > are all moved over, that dependency will go away.
>
> Right. That's exactly what I meant. If we add depends on !HAVE_PWM to
> the PWM symbol that should result in both options conflicting, and
> therefore not being built at the same time.
But I would add it to all other ones then, not the generic one!
One question though: if the generic pwm implementation does not set
HAVE_PWM, how can a driver check its presence?
Arnd
next prev parent reply other threads:[~2012-06-30 20:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 7:48 linux-next: build failure after merge of the final tree (pwm tree related) Stephen Rothwell
2012-06-30 18:10 ` Thierry Reding
2012-06-30 19:20 ` Arnd Bergmann
2012-06-30 19:41 ` Thierry Reding
2012-06-30 20:12 ` Arnd Bergmann [this message]
2012-07-01 6:56 ` Thierry Reding
2012-07-03 5:43 ` Stephen Rothwell
2012-07-03 6:11 ` Thierry Reding
2012-07-03 6:18 ` Stephen Rothwell
2012-07-03 6:23 ` Thierry Reding
2012-07-03 8:06 ` Arnd Bergmann
2012-07-03 8:11 ` Thierry Reding
2012-07-03 8:59 ` Arnd Bergmann
2012-07-03 10:00 ` Thierry Reding
2012-07-03 11:06 ` Arnd Bergmann
2012-07-03 11:14 ` Thierry Reding
2012-07-03 8:23 ` Geert Uytterhoeven
2012-07-03 9:00 ` Arnd Bergmann
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=201206302012.32476.arnd.bergmann@linaro.org \
--to=arnd.bergmann@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sfr@canb.auug.org.au \
--cc=thierry.reding@avionic-design.de \
/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.