From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: [git pull] x86 updates for v2.6.28, phase #1
Date: Fri, 10 Oct 2008 17:26:31 +0200 [thread overview]
Message-ID: <20081010152631.GB26231@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.00.0810100808540.3524@nehalem.linux-foundation.org>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Fri, 10 Oct 2008, Ingo Molnar wrote:
> >
> > Vegard Nossum (3):
> > x86: consolidate header guards
> > x86: consolidate header guards
>
> Ok, so I pulled phase 1, but quite frankly, I think this was utter
> crap. Why the hell did this go in?
we'll fix that up. We'll move all header files to arch/x86/include/asm/
anyway later in the merge window, once the dust settles, and can do a
separate commit for this as well.
The main motivation was that we had a few incidents of missing header
guards and Vegard asked whether he should script up some complete commit
that adds guards to all files and i agreed and didnt look closely enough
- my bad.
this aspect of it:
-#ifndef _ASM_X86_I387_H
-#define _ASM_X86_I387_H
+#ifndef ASM_X86__I387_H
+#define ASM_X86__I387_H
is indeed broken and deviates from the established convention of the
header guards as well.
> And yes, yes, we could add the f*cking things back when we export them
> as header files, but what's the point, really? And no, I'm not
> guaranteeing that we're being super-careful about namespace issues in
> all kernel headers that can get exported to user space, but we _try_.
yes, agreed. Sorry about that, it slipped through. (It was one of our
first real Git pulls and i meanwhile learned to look at them much more
carefully.)
It's completely my fault because Vegard offered multiple iterations of
the script and asked us precisely what we wanted.
Ingo
next prev parent reply other threads:[~2008-10-10 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 23:47 Ingo Molnar
2008-10-10 15:15 ` Linus Torvalds
2008-10-10 15:26 ` Ingo Molnar [this message]
2008-10-10 15:58 ` Ingo Molnar
2008-10-10 20:39 ` Vegard Nossum
2008-10-10 20:43 ` H. Peter Anvin
2008-10-10 21:07 ` Linus Torvalds
2008-10-10 21:21 ` H. Peter Anvin
2008-10-10 21:37 ` malc
2008-10-10 20:47 ` Ingo Molnar
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=20081010152631.GB26231@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®