From: Michal Marek <mmarek@suse.cz>
To: cody@linux.vnet.ibm.com
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kconfig: allow long lines in config file
Date: Fri, 13 Jul 2012 22:54:53 +0200 [thread overview]
Message-ID: <20120713205447.GA5160@pobox.suse.cz> (raw)
In-Reply-To: <1342204033-24484-1-git-send-email-cody@linux.vnet.ibm.com>
On Fri, Jul 13, 2012 at 11:27:12AM -0700, cody@linux.vnet.ibm.com wrote:
> From: Cody Schafer <cody@linux.vnet.ibm.com>
>
> For some config options (CONFIG_EXTRA_FIRMWARE, for example), the length
> of a config file line can exceed the 1024 byte buffer.
>
> Switch from fgets to compat_getline to fix. compat_getline is an
> internally implimented getline work-alike for portability purposes.
>
> Signed-off-by: Cody Schafer <cody@linux.vnet.ibm.com>
Applied to kbuild.git#kconfig, thanks.
Michal
next prev parent reply other threads:[~2012-07-13 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 23:47 [PATCH] kconfig: allow long lines in config file cody
2012-07-13 13:07 ` Michal Marek
2012-07-13 18:27 ` [PATCH v2] " cody
2012-07-13 20:54 ` Michal Marek [this message]
2012-07-13 18:30 ` [PATCH] " cody
2012-07-13 20:39 ` 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=20120713205447.GA5160@pobox.suse.cz \
--to=mmarek@suse.cz \
--cc=cody@linux.vnet.ibm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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