From: Peter Foley <pefoley2@verizon.net>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
mmarek@suse.cz, gxt@mprc.pku.edu.cn
Subject: Re: [PATCH] kbuild: mark unicore32 header export as broken
Date: Tue, 26 Apr 2011 17:04:23 -0400 [thread overview]
Message-ID: <4DB73357.5020403@verizon.net> (raw)
In-Reply-To: <BANLkTikFUhiDSEM_yLtbzmhfdUWBDv71ww@mail.gmail.com>
On 4/26/2011 1:07 PM, Américo Wang wrote:
> On Tue, Apr 26, 2011 at 2:48 PM, Arnaud Lacombe <lacombar@gmail.com> wrote:
>> Hi,
>>
>> On Sun, Apr 24, 2011 at 7:15 PM, Peter Foley <pefoley2@verizon.net> wrote:
>>> This patch marks userspace header export for unicore32 as broken so that
>>> it is skipped when running make headers_install_all.
>>>
>> Why ?
>>
>> I would expect you to send this to arch/unicore32 maintainer too, he
>> is not in the CC: list.
>
> +1
>
> If you see errors when install kernel headers on unicore32, fix them instead
> of marking it as broken.
The problem with unicore32 is that it generates various stub headers at compile time in include/generated/asm.
I believe the unicore32 maintainer is already aware of headers_install not working (see https://lkml.org/lkml/2011/1/8/11).
I'm adding him to the CC list on this email.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Foley <pefoley2@verizon.net>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-kbuild@vger.kernel.org>,
<mmarek@suse.cz>, <gxt@mprc.pku.edu.cn>
Subject: Re: [PATCH] kbuild: mark unicore32 header export as broken
Date: Tue, 26 Apr 2011 17:04:23 -0400 [thread overview]
Message-ID: <4DB73357.5020403@verizon.net> (raw)
In-Reply-To: <BANLkTikFUhiDSEM_yLtbzmhfdUWBDv71ww@mail.gmail.com>
On 4/26/2011 1:07 PM, Américo Wang wrote:
> On Tue, Apr 26, 2011 at 2:48 PM, Arnaud Lacombe <lacombar@gmail.com> wrote:
>> Hi,
>>
>> On Sun, Apr 24, 2011 at 7:15 PM, Peter Foley <pefoley2@verizon.net> wrote:
>>> This patch marks userspace header export for unicore32 as broken so that
>>> it is skipped when running make headers_install_all.
>>>
>> Why ?
>>
>> I would expect you to send this to arch/unicore32 maintainer too, he
>> is not in the CC: list.
>
> +1
>
> If you see errors when install kernel headers on unicore32, fix them instead
> of marking it as broken.
The problem with unicore32 is that it generates various stub headers at compile time in include/generated/asm.
I believe the unicore32 maintainer is already aware of headers_install not working (see https://lkml.org/lkml/2011/1/8/11).
I'm adding him to the CC list on this email.
next prev parent reply other threads:[~2011-04-26 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 23:15 [PATCH] kbuild: mark unicore32 header export as broken Peter Foley
2011-04-24 23:15 ` Peter Foley
2011-04-26 6:48 ` Arnaud Lacombe
2011-04-26 17:07 ` Américo Wang
2011-04-26 21:04 ` Peter Foley [this message]
2011-04-26 21:04 ` Peter Foley
2011-04-27 2:02 ` Guan Xuetao
2011-04-27 2:02 ` Guan Xuetao
2011-04-26 20:36 ` Peter Foley
2011-04-26 20:36 ` Peter Foley
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=4DB73357.5020403@verizon.net \
--to=pefoley2@verizon.net \
--cc=gxt@mprc.pku.edu.cn \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=xiyou.wangcong@gmail.com \
/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.