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: <132b313f-ac2d-be4d-8ab7-84b114041722@suse.com>
Date:   Fri, 10 Mar 2017 11:15:26 +0100
From:   Michal Marek <mmarek@...e.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        masahiroy@...nel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Kbuild maintainership

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?

Thanks,
Michal