From: Matthew Wilcox <matthew@wil.cx>
To: "Yang, Bo" <Bo.Yang@lsi.com>
Cc: linux-scsi@vger.kernel.org, James.Bottomley@SteelEye.com,
akpm@osdl.org, linux-kernel@vger.kernel.org, "Patro,
Sumant" <Sumant.Patro@lsi.com>,
"Kolli, Neela" <Neela.Kolli@lsi.com>
Subject: Re: [PATCH 1/1] scsi: megaraid_sas - Fix random failure of DCDB cmds with sense info
Date: Wed, 28 Nov 2007 12:27:03 -0700 [thread overview]
Message-ID: <20071128192703.GA2584@parisc-linux.org> (raw)
In-Reply-To: <9738BCBE884FDB42801FAD8A7769C26501D33B5B@NAMAIL1.ad.lsil.com>
On Wed, Nov 28, 2007 at 12:08:37PM -0700, Yang, Bo wrote:
> Matthew,
>
> Yes, as I mentioned, our applications are built in 32-bit environment
> (except for ia64).
> We may see a different behavior if we build it in 64-bit for x86-64.
Then this patch isn't acceptable. You need to find a way which works
for both 32-bit and 64-bit applications.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-11-28 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 8:40 [PATCH 1/1] scsi: megaraid_sas - Fix random failure of DCDB cmds with sense info bo yang
2007-11-20 20:42 ` Matthew Wilcox
2007-11-27 15:19 ` Yang, Bo
2007-11-27 15:19 ` Yang, Bo
2007-11-27 15:32 ` Matthew Wilcox
2007-11-28 19:08 ` Yang, Bo
2007-11-28 19:08 ` Yang, Bo
2007-11-28 19:27 ` Matthew Wilcox [this message]
2007-11-29 18:24 ` Yang, Bo
2007-11-29 18:24 ` Yang, Bo
-- strict thread matches above, loose matches on Subject: below --
2008-02-22 16:17 Yang, Bo
2008-02-22 16:17 ` Yang, Bo
2008-02-22 16:24 ` Matthew Wilcox
2008-02-22 16:27 ` James Bottomley
2008-02-22 16:35 ` James Bottomley
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=20071128192703.GA2584@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Bo.Yang@lsi.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Neela.Kolli@lsi.com \
--cc=Sumant.Patro@lsi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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.