linux-kernel - Re: [PATCH] Promise 'stex' driver

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

Message-ID: <20060725092656.GA28195@infradead.org>
Date:	Tue, 25 Jul 2006 10:26:56 +0100
From:	hch <hch@...radead.org>
To:	Ed Lin <ed.lin@...mise.com>
Cc:	linux-scsi <linux-scsi@...r.kernel.org>,
	"James.Bottomley" <James.Bottomley@...elEye.com>,
	hch <hch@...radead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	akpm <akpm@...l.org>, promise_linux <promise_linux@...mise.com>,
	jeff <jeff@...zik.org>
Subject: Re: [PATCH] Promise 'stex' driver

On Tue, Jul 25, 2006 at 12:41:11PM +0800, Ed Lin wrote:
> 
> So it seems there are several possibilities here(regarding no.1 comment):
> 1.The bridge code is kept unchanged. And, as this is a violation to
> Linux tradition and requirement, it could not be admitted upstream.

We have more than enough precedence for poking the bridge that comes as
part of addon cards.  As long as the code makes sure it never pokes a bridge
of the same type that is not on the card (and I don't have the code in front
of me right now to check whether it's true) we can keep this code.  Please
make sure to add a big comment that explains what is going on in detail
and why it's okay in this special case.

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