From: Arnd Bergmann <arnd@arndb.de>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 3/3] truncate()/ftruncate() fix length argument on ia32 emulation.
Date: Sun, 18 Sep 2011 17:26:19 +0200 [thread overview]
Message-ID: <2572424.HyPu2df1S7@wuerfel> (raw)
In-Reply-To: <1316282477.5814.19.camel@localhost.localdomain>
On Saturday 17 September 2011 20:01:17 Thomas Meyer wrote:
> move signed-extended int to long, because of signed test.
>
> Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
I would expect that the same is needed on ia64 and parisc and mips.
powerpc, s390 and sparc probably don't need it because they
have architecture specific code that already does this, but you
can probably remove the powerpc version if you add a generic
one.
New architectures (including tile) won't need the wrapper because
the 32-bit ABI there only has truncate64.
Arnd
next prev parent reply other threads:[~2011-09-18 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 18:01 [PATCH 3/3] truncate()/ftruncate() fix length argument on ia32 emulation Thomas Meyer
2011-09-18 15:26 ` Arnd Bergmann [this message]
2011-09-19 13:16 ` Heiko Carstens
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=2572424.HyPu2df1S7@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.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;
as well as URLs for NNTP newsgroup(s).