From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"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>
Subject: Re: [git pull] x86 updates for v2.6.28, phase #1
Date: Fri, 10 Oct 2008 22:39:23 +0200 [thread overview]
Message-ID: <19f34abd0810101339x66afc6d3mb6efa1a52e186816@mail.gmail.com> (raw)
In-Reply-To: <20081010155830.GA4767@elte.hu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 2275 bytes --]
On Fri, Oct 10, 2008 at 5:58 PM, Ingo Molnar <mingo@elte.hu> wrote:>> * Ingo Molnar <mingo@elte.hu> wrote:>>> > 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.>> we'll do the commit below once we've moved the header files to> arch/x86/include/asm/. (doing it right now would conflict with various> existing branches so it would be nice to wait with this.)>> Ingo>> ---------------->> From 5f3a8db0d4b091521541153580454099618fec2c Mon Sep 17 00:00:00 2001> From: Ingo Molnar <mingo@elte.hu>> Date: Fri, 10 Oct 2008 17:51:28 +0200> Subject: [PATCH] x86: fix header guard naming ugliness>> as Linus has noticed, the underscore aspect of these changes in> 77ef50a ("x86: consolidate header guards") are bogus:>> -#ifndef _ASM_BOOT_H> -#define _ASM_BOOT_H> +#ifndef ASM_X86__BOOT_H> +#define ASM_X86__BOOT_H>> as Linus pointed out:>> 1) header guard symbols are internal symbols in a reserved namespace,> so a leading underscore is perfectly justified>> 2) user-space might accidentally stumble into the new symbols:>> #include <sys/types.h>>> int ASM_X86__TYPES_H = 1;>> plus this deviates from all the standard header guard naming we> use elsewhere in the kernel.
Note: If you don't want the double underscores anywhere, this patch isnot enough.
For example:
> -#endif /* ASM_X86__MACH_DEFAULT__MACH_TIMER_H */> +#endif /* _ASM_X86_MACH_DEFAULT__MACH_TIMER_H */
There are also a few non-trivial changes, which could break with anaïve sed script. So I suggest to simply revert it, it's a lot saferthan trying to patch it up in the last minute.
I'm obviously also sorry for causing this problem in the first place... *blush*
Vegard
-- "The animistic metaphor of the bug that maliciously sneaked in whilethe programmer was not looking is intellectually dishonest as itdisguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2008-10-10 20:39 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
2008-10-10 15:58 ` Ingo Molnar
2008-10-10 20:39 ` Vegard Nossum [this message]
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=19f34abd0810101339x66afc6d3mb6efa1a52e186816@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®