From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] tools: env: Use getline rather than fgets when reading config/script
Date: Wed, 13 Jun 2018 11:42:59 -0400 [thread overview]
Message-ID: <20180613154259.GG350@bill-the-cat.ec.rr.com> (raw)
In-Reply-To: <20180607122005.17506-1-alex.kiernan@gmail.com>
On Thu, Jun 07, 2018 at 12:20:05PM +0000, Alex Kiernan wrote:
> When reading the config file, or a script file, use getline rather than
> fgets so line lengths aren't limited by the size of a compiled in buffer
> (128 characters for config, 1024 for scripts).
>
> Rename 'dump' to 'line' so it's clear we're working with a line of text.
>
> Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180613/90ed65e5/attachment.sig>
prev parent reply other threads:[~2018-06-13 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 12:20 [U-Boot] [PATCH] tools: env: Use getline rather than fgets when reading config/script Alex Kiernan
2018-06-07 12:26 ` Lukasz Majewski
2018-06-13 15:42 ` Tom Rini [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=20180613154259.GG350@bill-the-cat.ec.rr.com \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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