From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <akpm@linux-foundation.org>,
<linux@arm.linux.org.uk>, <sam@ravnborg.org>,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH v2] compiler.h: Include <linux/bug.h> to avoid build breakage with ARRAY_SIZE()
Date: Fri, 2 Mar 2012 09:22:02 -0500 [thread overview]
Message-ID: <4F50D78A.1020209@windriver.com> (raw)
In-Reply-To: <CAOMZO5DYNdp=1h9WJ7QRBJSAe-pJEerVZmA0tro+7brhZi6PxQ@mail.gmail.com>
On 12-03-01 10:13 PM, Fabio Estevam wrote:
> On Thu, Mar 1, 2012 at 11:49 PM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
>
>> Thanks, but no.
>>
>> You missed the whole point of my previous comments -- that being
>> that we don't want to just jam headers into always-used headers.
>
> Yes, it is not clear for me how to fix this build error. I got
> different feedbacks from you, Russell and Sam.
Understood, there was some discussion there. Anyways it is already
dealt with in yesterday's linux-next tree, so you won't have the
build failure anymore.
Thanks,
Paul.
>
>> The compiler.h is going to be an "always used" header. So if we
>> can avoid stuffing it full of extra crap, we need to really try.
>
> So let me ask you: how do you want me to fix the build error I am seeing?
next prev parent reply other threads:[~2012-03-02 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 13:41 [PATCH] kernel.h: " Fabio Estevam
2012-02-28 15:51 ` Sam Ravnborg
2012-02-28 16:43 ` Paul Gortmaker
2012-02-28 20:06 ` Sam Ravnborg
2012-03-02 1:15 ` [PATCH v2] compiler.h: " Fabio Estevam
2012-03-02 2:49 ` Paul Gortmaker
2012-03-02 3:13 ` Fabio Estevam
2012-03-02 14:22 ` Paul Gortmaker [this message]
2012-04-04 14:29 ` Uwe Kleine-König
2012-04-05 18:35 ` Paul Gortmaker
2012-04-05 18:52 ` Uwe Kleine-König
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=4F50D78A.1020209@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sam@ravnborg.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
Powered by JetHome