From: Thierry Reding <thierry.reding@avionic-design•de>
To: Arnd Bergmann <arnd.bergmann@linaro•org>
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 21:41:40 +0200 [thread overview]
Message-ID: <20120630194139.GA24300@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <201206301920.21158.arnd.bergmann@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
On Sat, Jun 30, 2012 at 07:20:21PM +0000, Arnd Bergmann wrote:
> On Saturday 30 June 2012, Thierry Reding wrote:
> > I hadn't thought about the allyesconfig case yet. Adding a "depends on
> > !HAVE_PWM" to the PWM symbol should work and is the easiest fix to this
> > kind of problem while other PWM legacy API implementations are ported to
> > the PWM subsystem.
> >
> > Sascha, Arnd (Cc'ed): what do you think?
> >
> > I don't know if I'll get enough time to test this over the weekend but I
> > should get to it when I'm back in the office on Monday.
> >
> You cannot depend on a symbol in the same place that provides it -- that
> would be a recursive dependency (or a paradox).
The PWM symbol doesn't provide HAVE_PWM.
> 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.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-30 19:41 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 [this message]
2012-06-30 20:12 ` Arnd Bergmann
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=20120630194139.GA24300@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design$(echo .)de \
--cc=arnd.bergmann@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=s.hauer@pengutronix$(echo .)de \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox