From: Michal Marek <mmarek@suse.cz>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: David Daney <ddaney.cavm@gmail.com>,
Arnaud Lacombe <lacombar@gmail.com>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"Daney, David" <David.Daney@caviumnetworks.com>
Subject: Re: [PATCH] Kbuild: append missing-syscalls to the default target list
Date: Wed, 09 Nov 2011 14:43:31 +0100 [thread overview]
Message-ID: <4EBA8383.3020100@suse.cz> (raw)
In-Reply-To: <20111109095414.GA15438@linux-mips.org>
Dne 9.11.2011 10:54, Ralf Baechle napsal(a):
> On Tue, Nov 08, 2011 at 11:30:48PM +0100, Michal Marek wrote:
>
>> On 8.11.2011 19:21, David Daney wrote:
>>> The problem is that compiler options meant to be used only for the
>>> compiling done by scripts/checksyscalls.sh are now leaking into the
>>> compilation of other parts of the kernel (asm-offsets.c), where they
>>> wreak havoc.
>>>
>>> Something like the attached is what I think needs to be done.
>>
>> Ah, right. That makes a lot of sense now. Ralf, does the patch at
>> https://lkml.org/lkml/2011/11/8/312 work for you?
>
> Yes, it does - and unlike David's first version this one also looks
> reasonably elegant.
>
> Acked-by: Ralf Baechle <ralf@linux-mips.org>
Thanks to both of you, applied to kbuild.git#rc-fixes.
Michal
prev parent reply other threads:[~2011-11-09 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 1:03 [PATCH] Kbuild: append missing-syscalls to the default target list Arnaud Lacombe
2011-09-09 11:55 ` Michal Marek
2011-09-14 5:17 ` Arnaud Lacombe
2011-11-01 23:22 ` Michal Marek
2011-11-07 20:44 ` Ralf Baechle
2011-11-07 21:19 ` Michal Marek
2011-11-07 23:33 ` Ralf Baechle
2011-11-08 8:25 ` Michal Marek
2011-11-08 9:53 ` Ralf Baechle
2011-11-08 18:21 ` David Daney
2011-11-08 22:30 ` Michal Marek
2011-11-09 9:54 ` Ralf Baechle
2011-11-09 13:43 ` Michal Marek [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=4EBA8383.3020100@suse.cz \
--to=mmarek@suse.cz \
--cc=David.Daney@caviumnetworks.com \
--cc=ddaney.cavm@gmail.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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