From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] tools: mkenvimage: Fixes for reading from pipes
Date: Sun, 30 Jun 2019 10:40:44 -0400 [thread overview]
Message-ID: <20190630144044.GC9388@bill-the-cat> (raw)
In-Reply-To: <20190630014501.16027-1-andre.przywara@arm.com>
On Sun, Jun 30, 2019 at 02:44:59AM +0100, Andre Przywara wrote:
> This fixes two issues I had when trying to create an envimage from a
> more complex pipe:
> - The read process stops when the read(2) syscall returns less bytes
> than requested.
> - Specifying an input filename expects this to be a regular file.
>
> See the respective commit messages for more details.
>
> Thanks!
> Andre
>
> Andre Przywara (2):
> tools: mkenvimage: Fix reading from slow pipe
> tools: mkenvimage: Always consider non-regular files
>
> tools/mkenvimage.c | 71 ++++++++++++++++--------------------------------------
> 1 file changed, 21 insertions(+), 50 deletions(-)
These all look fine but in the interest of avoiding unintended
consequences I'm going to pull these in after v2019.07 as they're
long-standing bugs rather than regressions being fixed, 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/20190630/a2f17ee2/attachment.sig>
next prev parent reply other threads:[~2019-06-30 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 1:44 [U-Boot] [PATCH 0/2] tools: mkenvimage: Fixes for reading from pipes Andre Przywara
2019-06-30 1:45 ` [U-Boot] [PATCH 1/2] tools: mkenvimage: Fix reading from slow pipe Andre Przywara
2019-07-01 6:31 ` Alexander Dahl
2019-07-18 23:57 ` Tom Rini
2019-06-30 1:45 ` [U-Boot] [PATCH 2/2] tools: mkenvimage: Always consider non-regular files Andre Przywara
2019-07-18 23:57 ` Tom Rini
2019-06-30 14:40 ` Tom Rini [this message]
2019-07-01 9:22 ` [U-Boot] [PATCH 0/2] tools: mkenvimage: Fixes for reading from pipes Andre Przywara
2019-07-01 13:23 ` Tom Rini
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=20190630144044.GC9388@bill-the-cat \
--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 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.