linux-kernel - Re: [Scst-devel] Fwd: Re: linuxcon 2010...

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: <4C72CEB9.4000008@vlnb.net>
Date:	Mon, 23 Aug 2010 23:40:41 +0400
From:	Vladislav Bolkhovitin <vst@...b.net>
To:	Gennadiy Nerubayev <parakie@...il.com>
CC:	James Bottomley <James.Bottomley@...e.de>,
	scst-devel <scst-devel@...ts.sourceforge.net>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [Scst-devel] Fwd: Re: linuxcon 2010...

Gennadiy Nerubayev, on 08/23/2010 02:10 AM wrote:
> I'm not sure if I understand why there is a need for a replacement
> target to reuse existing code, and would definitely appreciate a brief
> explanation or a pointer to an earlier one. But even that aside, I'm
> curious if the criteria for what a replacement target must have for
> (at least potential) inclusion into the kernel were ever clearly
> outlined in the past. If they were, then there probably would have
> been things like interested contenders, deadlines, feature
> comparisons, code reviews, and so on, right?

A fair public review of SCST code with a fair _public_ comparison 
without any deals and conspiracy behind our back is, basically, all we 
are asking. Let the best code win.

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