From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: bugs on exotic archs
Date: Tue, 13 May 2014 15:36:15 +0200 [thread overview]
Message-ID: <201405131536.15870.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20140513082349.GL8951@x2.net.home>
On Tuesday 13 May 2014, Karel Zak wrote:
> On Mon, May 12, 2014 at 08:45:18PM +0200, Ruediger Meier wrote:
> > %ifarch ppc ppc64
> > hexdump
>
> this is not a bug, but the hexdump test disadvantage -- the output
> may be different on big-endian if the output is composed from more
> input bytes.
I've fixed the hexdump test partially
https://github.com/karelzak/util-linux/pull/76
cu,
Rudi
next prev parent reply other threads:[~2014-05-13 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 18:45 bugs on exotic archs Ruediger Meier
2014-05-13 8:23 ` Karel Zak
2014-05-13 13:36 ` Ruediger Meier [this message]
2014-05-29 15:01 ` Ruediger Meier
2014-05-29 15:25 ` [PATCH] tests: fix fdisk/bsd for big endian systems Ruediger Meier
2014-05-29 17:32 ` Ruediger Meier
2014-05-29 17:52 ` Ruediger Meier
2014-06-09 11:02 ` Karel Zak
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=201405131536.15870.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--cc=util-linux@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