From: Michal Marek <mmarek@suse.cz>
To: Kyle McMartin <kyle@redhat.com>
Cc: linux-kbuild@vger.kernel.org, rob@landley.net,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Kbuild: pass headers to headers_install.sh on stdin
Date: Thu, 06 Jun 2013 19:41:57 +0200 [thread overview]
Message-ID: <51B0C9E5.7030105@suse.cz> (raw)
In-Reply-To: <20130606170557.GQ14762@redacted.bos.redhat.com>
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.
Michal
next prev parent reply other threads:[~2013-06-06 17:42 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 [this message]
2013-06-06 17:55 ` Kyle McMartin
2013-06-06 17:59 ` Josh Boyer
2013-06-06 18:43 ` Michal Marek
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=51B0C9E5.7030105@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox