From: Michal Marek <mmarek@suse.cz>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
linux kbuild list <linux-kbuild@vger.kernel.org>
Subject: Re: strange build failure when kconfig symbol is bool but not when tristate
Date: Sun, 20 Nov 2011 14:59:44 +0100 [thread overview]
Message-ID: <4EC907D0.5040104@suse.cz> (raw)
In-Reply-To: <4EBD537C.9070908@xenotime.net>
On 11.11.2011 17:55, Randy Dunlap wrote:
> On 10/14/2011 11:08 PM, Arnaud Lacombe wrote:
>> Hi,
>>
>> On Sat, Oct 15, 2011 at 1:52 AM, Randy Dunlap <rdunlap@xenotime.net> wrote:
>>> On 10/14/2011 10:39 PM, Arnaud Lacombe wrote
>>>> There was something like this not too long ago, does this:
>>>>
>>>> https://github.com/lacombar/linux-2.6/tree/master/kconfig/expr-woes
>>>>
>>>> helps ?
>>>
>>> Am I supposed to use that full kernel tree?
>>> Can I just get a patch to test?
>>>
>> You can merge that with whatever kernel tree. Sending the proper patch
>> has been on my TODO for a while
>
> Can we get a testable patch for this?
> or can we get this merged into linux-next so that I can test it?
You can do
$ git checkout -b kconfig-test v3.1
$ git pull git://github.com/lacombar/linux-2.6.git master/kconfig/expr-woes
and test if your bug is fixed.
Michal
next prev parent reply other threads:[~2011-11-20 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 22:31 strange build failure when kconfig symbol is bool but not when tristate Randy Dunlap
2011-10-14 22:54 ` Michal Marek
2011-10-15 0:20 ` Randy Dunlap
2011-10-15 5:39 ` Arnaud Lacombe
2011-10-15 5:52 ` Randy Dunlap
2011-10-15 6:08 ` Arnaud Lacombe
2011-11-11 16:55 ` Randy Dunlap
2011-11-20 13:59 ` Michal Marek [this message]
2011-11-20 17:39 ` Randy Dunlap
2011-11-20 18:02 ` Arnaud Lacombe
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=4EC907D0.5040104@suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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