public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Kbuild maintainership
Date: Mon, 13 Mar 2017 11:40:35 +0100	[thread overview]
Message-ID: <618aa552-8096-d350-e265-b6da26fb94a3@suse.com> (raw)
In-Reply-To: <CAK7LNAS+YHOgPG4y6x6L+Cc0A2=kH9Ndtc0gVMKtX5UgtLk_9g@mail.gmail.com>

On 2017-03-11 06:45, Masahiro Yamada wrote:
> Hi Michal,
> 
> 2017-03-10 19:15 GMT+09:00 Michal Marek <mmarek@suse.com>:
>> On 2017-03-10 10:17, Stephen Rothwell wrote:
>>> 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?
>>
>> There is one genksyms fix in kbuild.git#kbuild which is not in mainline.
>> Masahiro, can you please pull it into your tree and give Stephen the url
>> and branches?
> 
> 
> Pulled into the (new)  linux-kbuild/kbuild

Thank you!

Michal


  reply	other threads:[~2017-03-13 10:40 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
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 [this message]
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=618aa552-8096-d350-e265-b6da26fb94a3@suse.com \
    --to=mmarek@suse.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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