From: Michal Marek <mmarek@suse.com>
To: Markus Mayer <mmayer@broadcom.com>
Cc: "Yann E. Morin" <yann.morin.1998@free.fr>,
Sam Ravnborg <sam@ravnborg.org>,
Linux Kbuild <linux-kbuild@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [RESEND PATCH] kconfig: allow kconfig to handle longer path names
Date: Thu, 10 Dec 2015 11:07:32 +0100 [thread overview]
Message-ID: <56694EE4.2040108@suse.com> (raw)
In-Reply-To: <1449701772-25095-1-git-send-email-mmayer@broadcom.com>
On 2015-12-09 23:56, Markus Mayer wrote:
> The current (arbitrary) limit of 128 characters for path names has
> proven too short for Android builds, as longer path names are used
> there.
>
> Change conf.c, so it can handle path lengths up to PATH_MAX characters.
>
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> ---
> scripts/kconfig/conf.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
Thanks, applied to kbuild.git#kconfig.
Michal
prev parent reply other threads:[~2015-12-10 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 22:56 [RESEND PATCH] kconfig: allow kconfig to handle longer path names Markus Mayer
2015-12-10 10:07 ` 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=56694EE4.2040108@suse.com \
--to=mmarek@suse.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=sam@ravnborg.org \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).