From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [patch] ia64: fix potential NaT bit error for sys_pipe().
Date: Mon, 24 Jan 2005 06:40:21 +0000 [thread overview]
Message-ID: <16884.38997.209621.947323@napali.hpl.hp.com> (raw)
In-Reply-To: <16878.2168.388519.26567@napali.hpl.hp.com>
>>>>> On Fri, 21 Jan 2005 10:48:46 -0800, "Chen, Kenneth W" <kenneth.w.chen@intel.com> said:
Ken> +.mem.offset 0,0; (p6) st8 [r2]=r8 // store return value in slot for r8
Ken> +.mem.offset 8,0; (p6) st8 [r3]=r0 // clear error indication in slot for r10
Without the .mem.offset, please?
--david
next prev parent reply other threads:[~2005-01-24 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 7:12 [patch] ia64: fix potential NaT bit error for sys_pipe() David Mosberger
2005-01-20 17:52 ` David Mosberger
2005-01-20 19:00 ` Seth, Rohit
2005-01-20 23:22 ` Seth, Rohit
2005-01-20 23:51 ` David Mosberger
2005-01-21 3:32 ` Chen, Kenneth W
2005-01-21 18:48 ` Chen, Kenneth W
2005-01-24 6:40 ` David Mosberger [this message]
2005-01-24 19:17 ` David Mosberger
2005-01-24 19:32 ` Chen, Kenneth W
2005-01-24 19:43 ` David Mosberger
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=16884.38997.209621.947323@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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