linux-kernel - Re: Kbuild maintainership

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK7LNARSvhpvq2Tbhym+uxt-7pbz3h0s+p1V14bGe6gj8nLCMg@mail.gmail.com>
Date:   Fri, 10 Mar 2017 19:29:17 +0900
From:   Masahiro Yamada <yamada.masahiro@...ionext.com>
To:     Michal Marek <mmarek@...e.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Kbuild maintainership

Hi Michal,


2017-03-10 19:15 GMT+09:00 Michal Marek <mmarek@...e.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?

I have been wondering how itshould be handled.

(and I had already sent a question about this to your suse.com address.
I am guessing it has not reached to you, yet.)


I will pull the branch into the new repository.

Thanks!

-- 
Best Regards
Masahiro Yamada