Stepping down as kbuild maintainer

Stepping down as kbuild maintainer

[Sam Ravnborg]

It has been fun to be kbuild maintainer but
as things stand right now I do not have the
time needed to be kbuild maintainer.

I have done this solely on a hobbyist basis
and family (3 kids etc) + job require me
so the kbuild maintainer job was becoming
a duty and not that fun suddenly.

Any linux related job required either
a move or too much working at home so
I drpped this idea.

So I decided to step down as maintainer
and I hope someone else can pick up.

What do I left "Orphan" as MAINTAINERS say?

I do not get many complains about kbuild these
days. All the basic stuff just works.

The only major complains are:
- no human can understand the kbuild files
  [Makefile, scripts/Makefile.*]
- select does not work (that kconfig btw)
- how to do strange this when building an external module

So I feel pretty confident that things does not blow
up on you when I leave.

I keep my mail address and will be reachable there.

Good luck!

	Sam

[PATCH] kbuild: Steppeing down as Maintainer

[Sam Ravnborg]

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.

Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
---
diff --git a/MAINTAINERS b/MAINTAINERS
index c824b4d..147ec86 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2987,11 +2987,8 @@ S:	Maintained
 F:	fs/autofs4/
 
 KERNEL BUILD
-M:	Sam Ravnborg <sam@ravnborg.org>
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-next.git
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes.git
 L:	linux-kbuild@vger.kernel.org
-S:	Maintained
+S:	Orphan
 F:	Documentation/kbuild/
 F:	Makefile
 F:	scripts/Makefile.*

Re: [PATCH] kbuild: Steppeing down as Maintainer

[tytso]

On Fri, Nov 20, 2009 at 07:26:13PM +0100, Sam Ravnborg 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.

Sam, thanks for all of your efforts.  The work you've done on Kbuild
has definitely been a real contribution to Linux.

Best regards, and hopefully you'll find some other projects that fit
within your family commitments as well as being more fun than burden!

       	    	   	       	       - Ted

Re: Stepping down as kbuild maintainer

[David Miller]

From: Sam Ravnborg <sam@ravnborg.org>
Date: Fri, 20 Nov 2009 19:22:49 +0100

> It has been fun to be kbuild maintainer but
> as things stand right now I do not have the
> time needed to be kbuild maintainer.

Thank you for all of your hard work Sam.

Re: Stepping down as kbuild maintainer

[Américo Wang]

On Fri, Nov 20, 2009 at 07:22:49PM +0100, Sam Ravnborg wrote:
>It has been fun to be kbuild maintainer but
>as things stand right now I do not have the
>time needed to be kbuild maintainer.
>
>I have done this solely on a hobbyist basis
>and family (3 kids etc) + job require me
>so the kbuild maintainer job was becoming
>a duty and not that fun suddenly.
>
>Any linux related job required either
>a move or too much working at home so
>I drpped this idea.


Hi, Sam,

Huge thanks to you for what you did for Linux
kernel! You did quite well.

It's a pity that we can't continue to work
with you.


>
>So I decided to step down as maintainer
>and I hope someone else can pick up.

I don't think i am able to take this but at
least I can take care of most of the scripts
under scripts/.


>
>I keep my mail address and will be reachable there.
>

Thanks again, Sam! Best wishes!

-- 
Live like a child, think like the god.
 

Re: Stepping down as kbuild maintainer

[Randy Dunlap]

On Sat, 21 Nov 2009 17:48:54 +0800 Américo Wang wrote:

> On Fri, Nov 20, 2009 at 07:22:49PM +0100, Sam Ravnborg wrote:
> >It has been fun to be kbuild maintainer but
> >as things stand right now I do not have the
> >time needed to be kbuild maintainer.
> >
> >I have done this solely on a hobbyist basis
> >and family (3 kids etc) + job require me
> >so the kbuild maintainer job was becoming
> >a duty and not that fun suddenly.
> >
> >Any linux related job required either
> >a move or too much working at home so
> >I drpped this idea.
> 
> 
> Hi, Sam,
> 
> Huge thanks to you for what you did for Linux
> kernel! You did quite well.
> 
> It's a pity that we can't continue to work
> with you.

Ditto, thanks much for your work here, Sam.


> >So I decided to step down as maintainer
> >and I hope someone else can pick up.
> 
> I don't think i am able to take this but at
> least I can take care of most of the scripts
> under scripts/.
> 
> 
> >
> >I keep my mail address and will be reachable there.
> >
> 
> Thanks again, Sam! Best wishes!

Ack that also.

---
~Randy

Re: Stepping down as kbuild maintainer

[Aníbal Monsalve Salazar]

On Sat, Nov 21, 2009 at 08:46:14AM +0100, Sam Ravnborg wrote:
>On Sat, Nov 21, 2009 at 12:44:47PM +1100, Aníbal Monsalve Salazar wrote:
>>Will you be available to answer questions while I walk the learning
>>curve? :)
>
>I will be around yes - as long as you do not expect too quick answers.
>Good luck(*) if you decide to try it!

On Sat, Nov 21, 2009 at 09:56:39PM +0800, Américo Wang wrote:
>On Sat, Nov 21, 2009 at 09:51:12PM +1100, Aníbal Monsalve Salazar wrote:
>>I assume you can also help with most of the scripts. Right? :)
>
>Sure, feel free to contact me if you need.

I would like to maintain kbuild.

Ram Ravnborg and Américo Wang are willing to help me.

Re: Stepping down as kbuild maintainer

[Steven Rostedt]

On Sun, Nov 22, 2009 at 09:44:45AM +1100, Aníbal Monsalve Salazar wrote:
> On Sat, Nov 21, 2009 at 08:46:14AM +0100, Sam Ravnborg wrote:
> >On Sat, Nov 21, 2009 at 12:44:47PM +1100, Aníbal Monsalve Salazar wrote:
> >>Will you be available to answer questions while I walk the learning
> >>curve? :)
> >
> >I will be around yes - as long as you do not expect too quick answers.
> >Good luck(*) if you decide to try it!

Sam, thanks for all your work!

> 
> On Sat, Nov 21, 2009 at 09:56:39PM +0800, Américo Wang wrote:
> >On Sat, Nov 21, 2009 at 09:51:12PM +1100, Aníbal Monsalve Salazar wrote:
> >>I assume you can also help with most of the scripts. Right? :)
> >
> >Sure, feel free to contact me if you need.
> 
> I would like to maintain kbuild.
> 
> Ram Ravnborg and Américo Wang are willing to help me.

I'm also willing to help out. I've been planning on taking the big plunge 
into the kbuild system anyway.

-- Steve

Re: Stepping down as kbuild maintainer

[Michal Marek]

Aníbal Monsalve Salazar napsal(a):
> On Sat, Nov 21, 2009 at 08:46:14AM +0100, Sam Ravnborg wrote:
>> On Sat, Nov 21, 2009 at 12:44:47PM +1100, Aníbal Monsalve Salazar wrote:
>>> Will you be available to answer questions while I walk the learning
>>> curve? :)
>> I will be around yes - as long as you do not expect too quick answers.
>> Good luck(*) if you decide to try it!
> 
> On Sat, Nov 21, 2009 at 09:56:39PM +0800, Américo Wang wrote:
>> On Sat, Nov 21, 2009 at 09:51:12PM +1100, Aníbal Monsalve Salazar wrote:
>>> I assume you can also help with most of the scripts. Right? :)
>> Sure, feel free to contact me if you need.
> 
> I would like to maintain kbuild.

Hi,

I would also like to maintain kbuild. Maybe we could work together? What
do you think? I already talked with Sam:

> On Mon, Nov 23, 2009 at 03:55:29PM +0100, Michal Marek wrote:
> > I would be interested / willing to take over kbuild maintainership
> > either alone or together with Aníbal who also expressed his interest. I
> > do have a linux-related job, actually kbuild-related (maintaining kernel
> > build infrastructure at a certain linux vendor) and my boss would allow
> > me to work on kbuild. I think have good experience with the kbuild
> > scripts, GNU make, perl, etc. Looking at the number of patches sent to
> > linux-kbuild, I think I should be able to manage that. And I only have
> > one kid so far ;-).
> 
> It helps enourmously if you anyway have do to some of the time consuming
> things at work.
> I suggest you and An?bal work out how to deal with stuff.
> 
> I will ocntinue to be around and can answer any questions - but the
> learning curve is maybe a bit steep in the beginning but then things
> gets easy.
> 
> And you are right - it has not been the # of patches to take care
> of. Only that to do stuff properly you should:
> - review carefully
> - test on 5+ architectures
> - and be responsive
> 
> So if you can put time aside for this a few times a week and maybe
> even the possibility to concentrate on something for more than 1 hour
> in row you should be fine.
> 
> Good luck!
> 
> 	Sam


Also, how is it supposed to work now technically - should we create a
new kbuild-{next,fixes}.git $somewhere, copy over the bits that are
currently in Sam's trees and start collecting & reviewing patches? And
once it's good enough, update the MAINTAINERS file?

Michal

Re: Stepping down as kbuild maintainer

[Jeffrey Haemer]

On Sun, 22 Nov 2009 09:44:45 +1100, Aníbal Monsalve Salazar wrote:
> I would like to maintain kbuild.
>
> Ram Ravnborg and Américo Wang are willing to help me.

I'm also willing to pitch in and help, though I'll need some guidance.

-- 
Click to Call Me Now! -- http://seejeffrun.blogspot.com/2009/09/call-me-now.html

Jeffrey Haemer <jeffrey.haemer@gmail.com>
720-837-8908 [cell],  @goyishekop [twitter]
http://www.youtube.com/user/goyishekop [vlog]

Re: Stepping down as kbuild maintainer

[H. Peter Anvin]

On 11/20/2009 10:22 AM, Sam Ravnborg wrote:
> It has been fun to be kbuild maintainer but
> as things stand right now I do not have the
> time needed to be kbuild maintainer.

Sam, thank you for all your work, and it is sad to see you go.

	-hpa

Re: [PATCH] kbuild: Steppeing down as Maintainer

[Andrew Morton]

On Fri, 20 Nov 2009 19:26:13 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:

>  KERNEL BUILD
> -M:	Sam Ravnborg <sam@ravnborg.org>
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-next.git
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes.git
>  L:	linux-kbuild@vger.kernel.org
> -S:	Maintained
> +S:	Orphan
>  F:	Documentation/kbuild/
>  F:	Makefile
>  F:	scripts/Makefile.*

Sigh.  Perhaps if I don't apply the patch, this won't happen?

And thanks for all the fish.  I'll continue to scoop up patches as I
see them and shall cc yourself and linux-kbuild and Anibal, Steve and
Michal on them and I shall wait and see what happens.


The current queue is:

kbuild-generate-modulesbuiltin.patch
kbuild-rebuild-fix-for-makefilemodbuiltin.patch
kbuild-generate-modulesbuiltin-fix-2.patch
kbuild-generate-modulesbuiltin-fix-2-checkpatch-fixes.patch
kconfig-cross_compile-option.patch
kbuild-clean-up-marker.patch
kbuild-clear-marker-out-of-modpost.patch
kbuild-genksyms-properly-consider-export_unused_symbol_gpl.patch


If at all possible, please do keep an eye on things as they fly past -
I think we'll find that a few words of insight from you on particular
issues can potentially save others a large amount of work, and can
steer us away from costly mistakes.

Thanks.

Re: [PATCH] kbuild: Steppeing down as Maintainer

[maximilian attems]

On Mon, Nov 23, 2009 at 03:05:24PM -0800, Andrew Morton wrote:
> 
> The current queue is:
> 
> kbuild-generate-modulesbuiltin.patch
> kbuild-rebuild-fix-for-makefilemodbuiltin.patch
> kbuild-generate-modulesbuiltin-fix-2.patch
> kbuild-generate-modulesbuiltin-fix-2-checkpatch-fixes.patch
> kconfig-cross_compile-option.patch
> kbuild-clean-up-marker.patch
> kbuild-clear-marker-out-of-modpost.patch
> kbuild-genksyms-properly-consider-export_unused_symbol_gpl.patch
> 
> 

please add the following fakeroot usage to -next for 2.6.33 as
package target enhancement:
http://marc.info/?l=linux-kbuild&m=125561337922614&w=2
http://marc.info/?l=linux-kbuild&m=125561358622933&w=2

patch got tested inbetween and with both acks:
Acked-by: Frans Pop <elendil@planet.nl>
Acked-by: maximilian attems <max@stro.at>
see http://marc.info/?l=linux-kbuild&m=125551864712151&w=2

thanks

Re: [PATCH] kbuild: Steppeing down as Maintainer

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]

Hi Sam,

On Fri, 20 Nov 2009 19:26:13 +0100 Sam Ravnborg <sam@ravnborg.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@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: [PATCH] kbuild: Steppeing down as Maintainer

[Sam Ravnborg]

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@ravnborg.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?

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

Re: [PATCH] kbuild: Steppeing down as Maintainer

[Andrew Morton]

On Tue, 24 Nov 2009 10:15:47 +0100
maximilian attems <max@stro.at> wrote:

> On Mon, Nov 23, 2009 at 03:05:24PM -0800, Andrew Morton wrote:
> > 
> > The current queue is:
> > 
> > kbuild-generate-modulesbuiltin.patch
> > kbuild-rebuild-fix-for-makefilemodbuiltin.patch
> > kbuild-generate-modulesbuiltin-fix-2.patch
> > kbuild-generate-modulesbuiltin-fix-2-checkpatch-fixes.patch
> > kconfig-cross_compile-option.patch
> > kbuild-clean-up-marker.patch
> > kbuild-clear-marker-out-of-modpost.patch
> > kbuild-genksyms-properly-consider-export_unused_symbol_gpl.patch
> > 
> > 
> 
> please add the following fakeroot usage to -next for 2.6.33 as
> package target enhancement:
> http://marc.info/?l=linux-kbuild&m=125561337922614&w=2
> http://marc.info/?l=linux-kbuild&m=125561358622933&w=2

I don't have a copy.

> patch got tested inbetween and with both acks:
> Acked-by: Frans Pop <elendil@planet.nl>
> Acked-by: maximilian attems <max@stro.at>
> see http://marc.info/?l=linux-kbuild&m=125551864712151&w=2

Please refresh, retest and resend.  Update the acks in the changelog, thanks.

Re: [PATCH] kbuild: Steppeing down as Maintainer

[Michal Marek]

Sam Ravnborg napsal(a):
> 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@ravnborg.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?
> 
> 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.

I took your kbuild-next.git and I'm going through the other patches
posted to linux-kbuild recently. I'll push the repo once passes some
testing.

Michal

Re: Stepping down as kbuild maintainer

[Aníbal Monsalve Salazar]

On Mon, Nov 23, 2009 at 10:09:52PM +0100, Michal Marek wrote:
>I would also like to maintain kbuild. Maybe we could work together?
>What do you think? I already talked with Sam:

(Sorry, I've been very busy with my Real Life. :)

Sure. I agree. I'll test the patches on my machines (i386, x86_64,
sparc64, powerpc, armel, alpha, and mips) and reply to them timely.

>>On Mon, Nov 23, 2009 at 03:55:29PM +0100, Michal Marek wrote:
>>>I would be interested / willing to take over kbuild maintainership
>>>either alone or together with Aníbal who also expressed his interest.
>>>I do have a linux-related job, actually kbuild-related (maintaining
>>>kernel build infrastructure at a certain linux vendor) and my boss
>>>would allow me to work on kbuild. I think have good experience with
>>>the kbuild scripts, GNU make, perl, etc. Looking at the number of
>>>patches sent to linux-kbuild, I think I should be able to manage
>>>that. And I only have one kid so far ;-).
>>
>>It helps enourmously if you anyway have do to some of the time
>>consuming things at work.
>>
>>I suggest you and Anibal work out how to deal with stuff.
>>
>>I will continue to be around and can answer any questions - but the
>>learning curve is maybe a bit steep in the beginning but then things
>>gets easy.
>>
>>And you are right - it has not been the # of patches to take care of.
>>Only that to do stuff properly you should:
>>- review carefully
>>- test on 5+ architectures
>>- and be responsive
>>
>>So if you can put time aside for this a few times a week and maybe
>>even the possibility to concentrate on something for more than 1 hour
>>in row you should be fine.

I agree with Sam too.

On Fri, Nov 27, 2009 at 03:22:11PM +1100, Stephen Rothwell wrote:
>You will need to ensure that the patches/commits in your tree/series
>have been:
>    * submitted under GPL v2 (or later) and include the Contributor's
>      Signed-off-by,
>    * posted to the relevant mailing list,
>    * reviewed by you (or another maintainer of your subsystem tree),
>    * successfully unit tested, and
>    * destined for the current or next Linux merge window.
>
>Basically, this should be just what you would send to Linus (or ask him
>to fetch).  It is allowed to be rebased if you deem it necessary.

And with Stephen as well.