From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michal Marek <mmarek@suse.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
masahiroy@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Kbuild maintainership
Date: Fri, 10 Mar 2017 20:17:02 +1100 [thread overview]
Message-ID: <20170310201702.47b0a523@canb.auug.org.au> (raw)
In-Reply-To: <dd914266-6ea1-3dd7-0531-0335bf3f723c@suse.com>
Hi Michal,
On Fri, 10 Mar 2017 09:48:44 +0100 Michal Marek <mmarek@suse.com> wrote:
>
> Dne 10.3.2017 v 03:07 Masahiro Yamada napsal(a):
> > Hello Kbuild contributors,
> >
> >
> > As you may notice, Michal has been busy since the beginning
> > of this year, and it has been getting difficult for him to
> > work on Kbuild on his regular basis.
>
> Yes, that's unfortunately the case.
>
>
> > Michal sent me an email a few days ago, and we discussed this locally.
> > Then, I decided to be a new maintainer of Kbuild. [1]
>
> Thanks a lot for this and I wish you good luck with this new challenge.
I assume that I will get a request to change the kbuild-current and
kbuilt trees in linux-next soon. In the meantime, should I remove the
current ones?
No rush though since I am on leave next week.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-03-10 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 2:07 Kbuild maintainership Masahiro Yamada
2017-03-10 8:48 ` Michal Marek
2017-03-10 9:17 ` Stephen Rothwell [this message]
2017-03-10 10:15 ` Michal Marek
2017-03-10 10:29 ` Masahiro Yamada
2017-03-11 5:45 ` Masahiro Yamada
2017-03-13 10:40 ` Michal Marek
2017-03-10 10:22 ` Masahiro Yamada
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=20170310201702.47b0a523@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mmarek@suse.com \
--cc=torvalds@linux-foundation.org \
--cc=yamada.masahiro@socionext.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox