From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
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: Wed, 16 Jul 2008 14:50:39 +0200 [thread overview]
Message-ID: <19f34abd0807160550v68aacb58nbdd46b0fe74c4704@mail.gmail.com> (raw)
In-Reply-To: <20080716115137.GA8075@elte.hu>
On Wed, Jul 16, 2008 at 1:51 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
>> * Vegard Nossum <vegard.nossum@gmail.com> wrote:
>>
>> > > or perhaps we could include it in tip/master right now as well, if
>> > > you did another branch that excluded the files below. That would
>> > > make merging a lot easier - and we could do a second phase in
>> > > v2.6.27-rc1. Hm?
>> >
>> > I don't think we really need to resolve conflicts at all. What we
>> > can do is simply to re-run the scripts against tip/master whenever
>> > you want the update.
>>
>> ok, lets do it that way.
>
> ... the right moment for this would be about now. Mind rerunning your
> scripts and create a pullable linux-2.6-headers tree, based on latest
> -git?
Aright! Here she is; you may pull the 'for-tip' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/vegard/linux-2.6-headers.git
for-tip
To see the result. This was based on tip/master. Shortlog:
Vegard Nossum (3):
x86: consolidate header guards
kvm: fix spurious '#' in header
kvm: consolidate header guard
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-07-16 12:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 21:45 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 [this message]
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
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=19f34abd0807160550v68aacb58nbdd46b0fe74c4704@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®