From: maximilian attems <maks@sternwelten.at>
To: James Bottomley <James.Bottomley@SteelEye.com>, 380272@bugs.debian.org
Cc: Kyle McMartin <kyle@parisc-linux.org>,
Joshua Rubin <joshua@rubixlinux.org>,
Matthew Wilcox <matthew@wil.cx>,
linux-scsi@vger.kernel.org, stable@kernel.org
Subject: Re: Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays
Date: Sat, 19 Aug 2006 20:27:26 +0200 [thread overview]
Message-ID: <20060819182726.GD4868@baikonur.stro.at> (raw)
In-Reply-To: <1155943138.3766.9.camel@mulgrave.il.steeleye.com>
On Fri, Aug 18, 2006 at 04:18:58PM -0700, James Bottomley wrote:
> On Fri, 2006-08-18 at 12:39 -0400, Kyle McMartin wrote:
> > The problem is because they both claim support for the same PCI Ids:
>
> That's this fix, isn't it?
>
> http://www.kernel.org/git/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=b2b3c121076961333977f485f0d54c22121df920
>
> James
added the stable Maintainers to cc,
please consider this patch for the next revision.
thanks
--
maks
next prev parent reply other threads:[~2006-08-19 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 15:59 Bug#380272: kernel-image-2.6-686-smp: cpqarray module fails to detect arrays Joshua Rubin
2006-08-18 16:39 ` Kyle McMartin
2006-08-18 23:18 ` James Bottomley
2006-08-18 23:28 ` Kyle McMartin
2006-08-19 18:27 ` maximilian attems [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-18 17:14 Joshua Rubin
2006-08-18 15:05 Joshua Rubin
2006-08-18 16:09 ` maximilian attems
2006-08-18 16:49 ` maximilian attems
2006-08-18 0:12 Joshua Rubin
[not found] <200607281800.59516.joshua@rubixlinux.org>
[not found] ` <200607301140.25691.joshua@rubixlinux.org>
[not found] ` <20060730200559.GO10814@baikonur.stro.at>
[not found] ` <200607301433.02983.joshua@rubixlinux.org>
2006-08-04 18:21 ` maximilian attems
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=20060819182726.GD4868@baikonur.stro.at \
--to=maks@sternwelten.at \
--cc=380272@bugs.debian.org \
--cc=James.Bottomley@SteelEye.com \
--cc=joshua@rubixlinux.org \
--cc=kyle@parisc-linux.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=stable@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