From: Christoph Hellwig <hch@infradead.org>
To: Jack Byer <ojbyer@usa.net>
Cc: Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org
Subject: Re: Fw: legacy megaraid driver bug in mm-series
Date: Tue, 13 Sep 2005 10:23:59 +0100 [thread overview]
Message-ID: <20050913092359.GA29552@infradead.org> (raw)
In-Reply-To: <432613BA.5060606@usa.net>
On Mon, Sep 12, 2005 at 07:48:10PM -0400, Jack Byer wrote:
> Andrew Morton wrote:
> > Christoph Hellwig <hch@infradead.org> wrote:
> >
> >>On Wed, Sep 07, 2005 at 02:52:58AM -0700, Andrew Morton wrote:
> >>
> >>>
> >>>Begin forwarded message:
> >>
> >>This looks preyyu much like a breakage because we're now always sending
> >>S/G list down the scsi layer.
> >>
> >>The patch below brings over code to handle that case from the megaraid_mbox
> >>driver. It's still wrong for the case someone sends a MODE_SENSE from
> >>highmem userspace, but it should at least boot with the patch applied.
> >>
> >
> >
> > Jack, have you had a chance to test this?
> >
> > Thanks.
> >
> Sorry, I spent the weekend whitewater rafting :) I will be able to test
> this patch on Wednesday. Which kernel versions should I apply this patch to?
I did it against the at that time latest scsi-misc tree. The old megaraid
driver hasn'tt changed much for a long time so it should apply against
any recent-ish tree.
next prev parent reply other threads:[~2005-09-13 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 9:52 Fw: legacy megaraid driver bug in mm-series Andrew Morton
2005-09-08 14:35 ` Christoph Hellwig
2005-09-09 23:58 ` Andrew Morton
2005-09-12 23:48 ` Jack Byer
2005-09-13 9:23 ` Christoph Hellwig [this message]
[not found] ` <4326A4A5.6090200@usa.net>
2005-09-14 18:14 ` Jack Byer
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 10:17 Jack Byer
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=20050913092359.GA29552@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ojbyer@usa.net \
/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.