From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 6280] new line of Xyratex RAID products and a patch to update for 2.4.x non-sequential LUN mapping
Date: Thu, 20 Mar 2008 06:52:38 -0700 (PDT) [thread overview]
Message-ID: <20080320135238.818C610803B@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-6280-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=6280
------- Comment #3 from anonymous@kernel-bugs.osdl.org 2008-03-20 06:52 -------
Reply-To: James.Bottomley@HansenPartnership.com
On Thu, 2008-03-20 at 00:34 -0700, bugme-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=6280
>
>
> protasnb@gmail.com changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |protasnb@gmail.com
> AssignedTo|scsi_drivers-other@kernel- |linux-scsi@vger.kernel.org
> |bugs.osdl.org |
>
>
>
>
> ------- Comment #2 from protasnb@gmail.com 2008-03-20 00:34 -------
> Petros,
> This bugzilla is about 2.6.XX. Do you think your patch makes sense for latest
> kernels, or this support is already implemented there?
Depends what SCSI level the array reports. If > 2 then the REPORT_LUNS
scan will already have taken care of all of this.
James
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-03-20 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-6280-11613@http.bugzilla.kernel.org/>
2008-03-20 7:34 ` [Bug 6280] new line of Xyratex RAID products and a patch to update for 2.4.x non-sequential LUN mapping bugme-daemon
2008-03-20 13:51 ` James Bottomley
2008-03-20 13:52 ` bugme-daemon [this message]
2008-03-20 16:53 ` bugme-daemon
2008-03-20 16:58 ` bugme-daemon
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=20080320135238.818C610803B@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox