From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v2.6.38-rc3
Date: Wed, 2 Feb 2011 20:19:14 +0000 [thread overview]
Message-ID: <20110202201913.GD28705@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTi=RZoqS1D3qQXJNupbBOcWLHdWiCNWmiVvvKV++@mail.gmail.com>
On Wed, Feb 02, 2011 at 03:16:41PM -0500, Arnaud Lacombe wrote:
> On Wed, Feb 2, 2011 at 3:10 PM, Mark Brown
> > Oh no, not another one :(
> Care to explain ?
It's a config option which is pretty much always has one setting and
causes build hassle if the other setting is chosen.
next prev parent reply other threads:[~2011-02-02 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 14:05 Build regressions/improvements in v2.6.38-rc3 Geert Uytterhoeven
2011-02-02 14:49 ` Mark Brown
2011-02-02 15:38 ` Geert Uytterhoeven
2011-02-02 20:06 ` Arnaud Lacombe
2011-02-02 20:10 ` Mark Brown
2011-02-02 20:16 ` Arnaud Lacombe
2011-02-02 20:19 ` Mark Brown [this message]
2011-02-02 20:26 ` Arnaud Lacombe
2011-02-02 18:20 ` Wolfram Sang
2011-02-27 18:20 ` Geert Uytterhoeven
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=20110202201913.GD28705@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=geert@linux-m68k.org \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox