[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091125172122.46beaf17.sfr@canb.auug.org.au>
Date: Wed, 25 Nov 2009 17:21:22 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kbuild: Steppeing down as Maintainer
Hi Sam,
On Fri, 20 Nov 2009 19:26:13 +0100 Sam Ravnborg <sam@...nborg.org> wrote:
>
> It has been fun but the last year or more it has
> been a duty and a burden. So I leave it open for
> other to take over.
I, also, want to thank you very much for all your work.
I am, however, wondering what will happen to the changes you have that are
currently in linux-next:
Apparently for v2.6.32 (in kbuild-current):
Michael Tokarev (1):
kbuild: fix bzImage build for x86
And queued for v2.6.33:
Sam Ravnborg (14):
kbuild: search arch/$ARCH/include before include/
dontdiff: add generated
kbuild: move bounds.h to include/generated
kbuild: move asm-offsets.h to include/generated
ia64: move nr-irqs.h to include/generated
arm: move mach-types to include/generated
sh: move machtypes.h to include/generated
kbuild: drop include2/ used for O=... builds
kbuild: do not check for include/asm-$ARCH
kbuild: drop include/asm
kbuild: move compile.h to include/generated
drop explicit include of autoconf.h
kbuild: move autoconf.h to include/generated
kbuild: move utsrelease.h to include/generated
I am (for the moment) still merging these from the copy I have of your
trees, but what to do in the longer term?
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists