From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] x86: more header fixes
Date: Tue, 22 Jul 2008 12:36:32 +0200 [thread overview]
Message-ID: <20080722103632.GA27029@elte.hu> (raw)
In-Reply-To: <20080722123231.GA13172@localhost.localdomain>
* Vegard Nossum <vegard.nossum@gmail.com> wrote:
> On Wed, Jul 16, 2008 at 4:22 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >> I'm not sure how we should proceed with this. On one hand, we could
> >> just fix the issues as they come up and be done with it. On the other
> >> hand, this was exactly the thing I wanted to avoid by automatic it. I
> >> guess it can never be fully automated... The question is if there is
> >> any danger of *silent* (read: runtime) breakage, which would be much
> >> worse than compiler errors.
> >
> > dont worry, lets fix the above hideous hack first, then i can merge the
> > guards fixes ontop of that fix. That's why we do testing, to catch the
> > cases where assumptions fail. Your script is just fine - it beats having
> > to edit 280+ files by hand ...
>
> I've updated my script to also fix any rogue uses of header-guard
> names in auxiliary files. I'm attaching the resulting patch.
>
> It doesn't really _fix_ the hideous hack, it merely unbreaks it.
>
> Patch #2 also fixes some left-over headers. They both apply on top of
> tip/x86/header-guards.
looks good - do you have a branch i could pull into
tip/x86/header-guards?
Ingo
next prev parent reply other threads:[~2008-07-22 10:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 21:45 [PATCH] x86: more header fixes Vegard Nossum
2008-06-18 10:30 ` Ingo Molnar
2008-06-18 16:19 ` Vegard Nossum
2008-06-26 12:02 ` Ingo Molnar
2008-06-26 13:30 ` Sam Ravnborg
2008-06-26 13:44 ` Vegard Nossum
2008-06-26 17:30 ` Sam Ravnborg
2008-06-26 16:53 ` Vegard Nossum
2008-07-01 9:28 ` Ingo Molnar
2008-07-16 11:51 ` Ingo Molnar
2008-07-16 12:50 ` Vegard Nossum
2008-07-16 13:08 ` Ingo Molnar
2008-07-16 13:17 ` Ingo Molnar
2008-07-16 13:46 ` Vegard Nossum
2008-07-16 14:22 ` Ingo Molnar
2008-07-22 12:32 ` Vegard Nossum
2008-07-22 10:36 ` Ingo Molnar [this message]
2008-07-22 11:13 ` Vegard Nossum
2008-07-22 11:38 ` Ingo Molnar
2008-07-22 18:27 ` Vegard Nossum
2008-07-26 13:08 ` 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=20080722103632.GA27029@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
--cc=x86@kernel.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