linux-kernel - Re: [PATCH v2 0/8] kbuild: various cleanups

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 for Android: free password hash cracker in your pocket

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

Date:   Thu, 8 Sep 2022 11:00:56 +0900
From:   Masahiro Yamada <masahiroy@...nel.org>
To:     Nicolas Schier <nicolas@...sle.eu>
Cc:     Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH v2 0/8] kbuild: various cleanups

On Thu, Sep 8, 2022 at 5:18 AM Nicolas Schier <nicolas@...sle.eu> wrote:
>
> On Wed, 7 Sep 2022 22:15:57 +0200 Nicolas Schier wrote:
> > On Tue,  6 Sep 2022 15:13:05 +0900 Masahiro Yamada wrote:
> > >
> > >  - Refactor single target build to make it work more correctly
> > >  - Link vmlinux and modules in parallel
> > >  - Remove head-y syntax
> > >
> > >
> > > Masahiro Yamada (8):
> > >   kbuild: fix and refactor single target build
> > >   kbuild: rename modules.order in sub-directories to .modules.order
> > >   kbuild: move core-y and drivers-y to ./Kbuild
> > >   kbuild: move .vmlinux.objs rule to Makefile.modpost
> > >   kbuild: move vmlinux.o rule to the top Makefile
> > >   kbuild: unify two modpost invocations
> > >   kbuild: use obj-y instead extra-y for objects placed at the head
> > >   kbuild: remove head-y syntax
> >
> > I'm not able to apply the patchset, neither on your current kbuild
> > branch nor on for-next.  What am I missing here?  Could you give me a
> > hint for a patchset base?
> >
> > Thanks and kind regards,
> > Nicolas
>
>
> ooops.  It _is_ already on kbuild, sorry for the noise.


Yes.
If you are happy to review and/or test the branch,
I will add Reviewed-by/Tested-by when I rebase it.




-- 
Best Regards
Masahiro Yamada