linux-kernel - Re: [PATCH] Kbuild: pass headers to headers

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]

Date:	Thu, 6 Jun 2013 13:59:21 -0400
From:	Josh Boyer <jwboyer@...il.com>
To:	Kyle McMartin <kyle@...hat.com>
Cc:	Michal Marek <mmarek@...e.cz>, linux-kbuild@...r.kernel.org,
	Rob Landley <rob@...dley.net>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Kbuild: pass headers to headers_install.sh on stdin

On Thu, Jun 6, 2013 at 1:55 PM, Kyle McMartin <kyle@...hat.com> wrote:
> On Thu, Jun 06, 2013 at 07:41:57PM +0200, Michal Marek wrote:
>> Dne 6.6.2013 19:05, Kyle McMartin napsal(a):
>> > While using make V=1 to test some things, I noticed on our builders that
>> > headers_install was failing because the argument list to /bin/sh was too
>> > long. Working around it is slightly kludgy...
>>
>> This is already fixed with
>>
>>
>> commit c0ff68f1611d6855a06d672989ad5cfea160a4eb
>> Author: Nicolas Dichtel <nicolas.dichtel@...nd.com>
>> Date:   Mon Apr 29 14:15:51 2013 +0200
>>
>>     kbuild: fix make headers_install when path is too long
>>
>>
>> in linux-next.
>>
>
> OK, I guess.

Wait... not OK.  This is broken now.  People are clearly having to fix
it again and wasting their time because a fix is already available.
Why is a fix for it sitting in linux-next?  Please get that fix into
Linus' tree.

josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/