All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Kyle McMartin <kyle@redhat.com>,
	linux-kbuild@vger.kernel.org, Rob Landley <rob@landley.net>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Kbuild: pass headers to headers_install.sh on stdin
Date: Thu, 06 Jun 2013 20:43:01 +0200	[thread overview]
Message-ID: <51B0D835.3050808@suse.cz> (raw)
In-Reply-To: <CA+5PVA4uNNSXcJHZfoyEmqMsCwK6hC7e2ziSdz5TNXwiiUQ7CQ@mail.gmail.com>

Dne 6.6.2013 19:59, Josh Boyer napsal(a):
> On Thu, Jun 6, 2013 at 1:55 PM, Kyle McMartin <kyle@redhat.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@6wind.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.

This bug has been there for about five years (as far as I can tell, it
was introduced by 7712401). It is a coincidence that two people report
it now within a couple of weeks, but IMO this does not make the bug so
urgent that it can't wait for the next -rc1.

Michal

      reply	other threads:[~2013-06-06 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 17:05 [PATCH] Kbuild: pass headers to headers_install.sh on stdin Kyle McMartin
2013-06-06 17:41 ` Michal Marek
2013-06-06 17:55   ` Kyle McMartin
2013-06-06 17:59     ` Josh Boyer
2013-06-06 18:43       ` Michal Marek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51B0D835.3050808@suse.cz \
    --to=mmarek@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=jwboyer@gmail.com \
    --cc=kyle@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.