From: Jim Rees <rees@umich.edu>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Benny Halevy <bhalevy@tonian.com>,
fanchaoting <fanchaoting@cn.fujitsu.com>,
Benny Halevy <benny@tonian.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] fix do_xor_speed 64-bit devision issue on 32-bits arch
Date: Sun, 25 Dec 2011 10:57:55 -0500 [thread overview]
Message-ID: <20111225155755.GB19792@umich.edu> (raw)
In-Reply-To: <4EF74056.2040306@panasas.com>
Boaz Harrosh wrote:
Please trash this patch for now. I will carry it out of tree for my use.
(Looks I'm the only one who's using UML and the XOR engine)
UML would explain it. Regular kernels should be ok.
next prev parent reply other threads:[~2011-12-25 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 14:08 [PATCH] fix do_xor_speed 64-bit devision issue on 32-bits arch Benny Halevy
2011-12-23 6:41 ` fanchaoting
2011-12-23 13:25 ` Jim Rees
2011-12-25 5:31 ` Benny Halevy
2011-12-25 13:54 ` Jim Rees
2011-12-25 15:25 ` Boaz Harrosh
2011-12-25 15:57 ` Jim Rees [this message]
2011-12-26 7:11 ` Benny Halevy
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=20111225155755.GB19792@umich.edu \
--to=rees@umich.edu \
--cc=benny@tonian.com \
--cc=bhalevy@tonian.com \
--cc=bharrosh@panasas.com \
--cc=fanchaoting@cn.fujitsu.com \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).