Re: [PATCH] kbuild: Steppeing down as Maintainer
From: Sam Ravnborg
Date: Wed Nov 25 2009 - 12:24:21 EST
On Wed, Nov 25, 2009 at 05:21:22PM +1100, Stephen Rothwell wrote:
> Hi Sam,
>
> On Fri, 20 Nov 2009 19:26:13 +0100 Sam Ravnborg <sam@xxxxxxxxxxxx> 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?
I will submit the patches like any other regular submitter to linux-kbuild
if the upcoming Maintainers does not pick them up from the git trees.
So for now keeping the pull would be nice but as soon as you have
a ew set of kbuild tress then drop these.
Frankly I had forgot that I had a patch in -fixes...
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/