All of lore.kernel.org
 help / color / mirror / Atom feed
From: paul.gortmaker@windriver.com (Paul Gortmaker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx51: Fix build error due to missing include of <linux/bug.h>
Date: Tue, 28 Feb 2012 18:52:45 -0500	[thread overview]
Message-ID: <20120228235244.GA3778@windriver.com> (raw)
In-Reply-To: <20120228132108.GB3617@n2100.arm.linux.org.uk>

[Re: [PATCH] ARM: mx51: Fix build error due to missing include of <linux/bug.h>] On 28/02/2012 (Tue 13:21) Russell King - ARM Linux wrote:

[...]

> The answer is not to start scattering lots of .c files with linux/bug.h
> includes, but to fix linux/kernel.h.

Hi Russell,

I understand your concerns, and had I found myself "buggering" lots
of .c files, I would have backed away and said to myself, "OK, this
really isn't going to work - we really can't do this."

But to put some metrics to it, after building for about 10 different
arch and all their defconfigs, I only had to change about twenty[1] of
the approximately sixteen thousand .c files in the kernel.  That is
about 0.125% -- which is one of the things that made me think "Hey, we
can really do this cleanup!"   Including this file, there were only
two .c files in all of arch/arm that were using bug somehow.

So I think having kernel.h not require bug.h is completely do-able.
But in the end, I'm not welded to the idea.  I think it is a win, but
I'm not going to kick up a big stink if Linus or Andrew say they don't
think it is of value, and would rather not rock the boat.

Thanks,
Paul.
--

[1] https://lkml.org/lkml/2012/1/26/521

  parent reply	other threads:[~2012-02-28 23:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 12:11 [PATCH] ARM: mx51: Fix build error due to missing include of <linux/bug.h> Fabio Estevam
2012-02-28 12:53 ` Russell King - ARM Linux
2012-02-28 13:03   ` Fabio Estevam
2012-02-28 13:21     ` Russell King - ARM Linux
2012-02-28 13:25       ` Fabio Estevam
2012-02-28 23:52       ` Paul Gortmaker [this message]
2012-02-29  0:06         ` Russell King - ARM Linux

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=20120228235244.GA3778@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.