linux-kernel - Re: [PATCH] x86: more header fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19f34abd0807160550v68aacb58nbdd46b0fe74c4704@mail.gmail.com>
Date:	Wed, 16 Jul 2008 14:50:39 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	"the arch/x86 maintainers" <x86@...nel.org>,
	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH] x86: more header fixes

On Wed, Jul 16, 2008 at 1:51 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Ingo Molnar <mingo@...e.hu> wrote:
>
>> * Vegard Nossum <vegard.nossum@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/