linux-kernel - Re: [PATCH 2/2] Workaround for SB600 SATA ODD issue

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061104183515.GA1675@infradead.org>
Date:	Sat, 4 Nov 2006 18:35:15 +0000
From:	Christoph Hellwig <hch@...radead.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Luugi Marsan <luugi.marsan@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Workaround for SB600 SATA ODD issue

On Sat, Nov 04, 2006 at 06:36:49PM +0100, Arjan van de Ven wrote:
> why put this into the ahci struct rather than in the pci device struct?
> In the place you use it you already have the pci device struct already..
> and it's really a pci device property so putting it in that struct makes
> a whole lot of sense conceptually anyway...

I think having a revision field in pci_dev that's initialized by the pci
code early on would be immensivly useful.  For now it probably makes sense
to do in ahci what all other drivers do and read it on it's own.

Adding it to the pci core and switching all the drivers over would
be a separate project.  Maybe we can sign AMD up for it as a general
kernel contribution thing? :)

-
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/