public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sat, 26 Jul 2008 15:08:40 +0200	[thread overview]
Message-ID: <20080726130840.GA14466@elte.hu> (raw)
In-Reply-To: <19f34abd0807221127q1c26fed7w5b276cadb7319fec@mail.gmail.com>


* Vegard Nossum <vegard.nossum@gmail.com> wrote:

> On Tue, Jul 22, 2008 at 1:38 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >> Though I still believe it should be squashed for bisectability.
> >
> > hm, i pulled it but 1ab9e368 cannot be squashed into aa27f9586 cleanly.
> 
> Yes, you are right. I forgot to check.
> 
> > I'd suggest the following approach, which we used for the scripted
> > unification of arch/x86. Do a couple of preparatory patches that just
> > bring all the header guards into proper shape. _Then_ run the script
> > against that "prepared" tree. The end result should be correct to the
> > best of our current knowledge. (i'll figure out any remaining build
> > breakages quickly - i can build 120+ random kernels per hour)
> >
> > We can rebase x86/header-guards to such a bisectable approach no problem
> > if you can do it like that, it's not yet merged anywhere. Just send me a
> > pull URI that i'll pull into a x86/header-guards that is reset back to
> > linus/master.
> >
> > Can you see any complications with that approach?
> 
> There's not really that much to prepare. But it really helps to work
> against the right tree to begin with :-)
> 
> So here's another one, this time prepared against linus/master, and
> fully bisectable by delaying the fixing of the headers which have
> external users of their guard-names. Check out the (new) 'for-tip'
> branch of
> 
>     git://git.kernel.org/pub/scm/linux/kernel/git/vegard/linux-2.6-headers.git
> 
> There are still headers left which have no guard at all; that's okay. 
> If they should be changed, it can be done later, it shouldn't make a 
> difference for now.

pulled into tip/x86/header-guards, thanks Vegard.

One small request: in the future, could you use git-request-pull to 
generate pull requests?

That way the full URI is included (otherwise it's easy to forget to add 
the 'for-tip' branch to the pull i do, etc.). Something like:

 git-request-pull linus/master \
  git://git.kernel.org/pub/scm/linux/kernel/git/vegard/linux-2.6-headers.git \
   for-tip

should do the trick. Thanks,

	Ingo

      reply	other threads:[~2008-07-26 13:09 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
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 [this message]

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=20080726130840.GA14466@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