All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: Steppeing down as Maintainer
Date: Wed, 25 Nov 2009 21:47:38 +0100	[thread overview]
Message-ID: <4B0D97EA.8040100@suse.cz> (raw)
In-Reply-To: <20091125172406.GA14085@merkur.ravnborg.org>

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

  reply	other threads:[~2009-11-25 20:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 18:22 Stepping down as kbuild maintainer Sam Ravnborg
2009-11-20 18:26 ` [PATCH] kbuild: Steppeing down as Maintainer Sam Ravnborg
2009-11-20 19:20   ` tytso
2009-11-23 23:05   ` Andrew Morton
2009-11-24  9:15     ` maximilian attems
2009-11-25 19:50       ` Andrew Morton
2009-11-25  6:21   ` Stephen Rothwell
2009-11-25 17:24     ` Sam Ravnborg
2009-11-25 20:47       ` Michal Marek [this message]
2009-11-20 21:56 ` Stepping down as kbuild maintainer David Miller
2009-11-21  9:48 ` Américo Wang
2009-11-21 17:07   ` Randy Dunlap
2009-11-21 22:44 ` Aníbal Monsalve Salazar
2009-11-23 15:08   ` Steven Rostedt
2009-11-23 21:09   ` Michal Marek
2009-11-29  7:09     ` Aníbal Monsalve Salazar
2009-11-23 21:37 ` H. Peter Anvin

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=4B0D97EA.8040100@suse.cz \
    --to=mmarek@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.