linux-kernel - RE: [PATCH 1/1] cciss: fix PCI IDs for new Smart Array controllers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0F5B06BAB751E047AB5C87D1F77A77887D0D850CD6@GVW0547EXC.americas.hpqcorp.net>
Date:	Mon, 18 Oct 2010 21:14:57 +0000
From:	"Miller, Mike (OS Dev)" <Mike.Miller@...com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Jens Axboe <axboe@...nel.dk>, LKML <linux-kernel@...r.kernel.org>,
	LKML-scsi <linux-scsi@...r.kernel.org>
Subject: RE: [PATCH 1/1] cciss: fix PCI IDs for new Smart Array controllers

 

> -----Original Message-----
> From: Andrew Morton [mailto:akpm@...ux-foundation.org] 
> Sent: Monday, October 18, 2010 2:56 PM
> To: Miller, Mike (OS Dev)
> Cc: Jens Axboe; LKML; LKML-scsi
> Subject: Re: [PATCH 1/1] cciss: fix PCI IDs for new Smart 
> Array controllers
> 
> On Mon, 18 Oct 2010 13:53:07 -0500
> Mike Miller <mike.miller@...com> wrote:
> 
> > Patch 1 of 1
> > cciss: fix PCI IDs for new controllers
> > 
> > This patch fixes the botched up PCI IDs of new controllers. Please 
> > consider this patch for inclusion.
> > 
> 
> What was botched up about it?
> 
> What are the runtime effects of this change?
> 
The PCI subsystem ID's were wrong. They were 3250 to 3254. They should have been 335x. I also added another new controller that just popped up.

The runtime effects are the boards will not be recognized without this fix.

-- mikem--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/