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: <CAK7LNASNtetbMkFWzbW69jh007B2R9dOzpYzgQ_xcFQj_ayVZA@mail.gmail.com>
Date:   Sat, 30 Mar 2019 21:11:33 +0900
From:   Masahiro Yamada <yamada.masahiro@...ionext.com>
To:     David Howells <dhowells@...hat.com>
Cc:     Al Viro <viro@...iv.linux.org.uk>, Andreas Schwab <schwab@...e.de>,
        linux-fsdevel@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 01/68] kbuild: skip sub-make for in-tree build with
 GNU Make 4.x

On Thu, Mar 28, 2019 at 9:53 AM Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
>
> David,
>
>
> On Thu, Mar 28, 2019 at 8:41 AM David Howells <dhowells@...hat.com> wrote:
> >
> > From: Masahiro Yamada <yamada.masahiro@...ionext.com>
> >
> > Commit 2b50f7ab6368 ("kbuild: add workaround for Debian make-kpkg")
> > annoyed people who want to wrap the top Makefile with GNUmakefile
> > or something in order to customize it for their use.
> >
> > On second thought, we do not need to run the sub-make for in-tree
> > build with Make 4.x because the 'MAKEFLAGS += -rR' issue only happens
> > on GNU Make 3.x.
> >
> > With this commit, people will get back the workflow, and the Debian
> > make-kpkg will still work.
> >
> > Fixes: 2b50f7ab6368 ("kbuild: add workaround for Debian make-kpkg")
> > Reported-by: Andreas Schwab <schwab@...e.de>
> > Reported-by: David Howells <dhowells@...hat.com>
> > Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>
> > Signed-off-by: David Howells <dhowells@...hat.com>
>
>
> Why should this patch be included in a
> totally unrelated patch series?
>
>
> I already applied this to my fixes branch,
> and am planning to send a PR to Linus soon.
>
> (Sorry, I missed to send a PR for -rc2)


Now, this landed in Linus tree.



-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ