linux-kernel - Re: [RFC PATCH 1/4] Mobile security processor 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100429211725.GA14909@kroah.com>
Date:	Thu, 29 Apr 2010 14:17:25 -0700
From:	Greg KH <greg@...ah.com>
To:	"Epshteyn, Eugene" <eugene.epshteyn@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 1/4] Mobile security processor driver


A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Thu, Apr 29, 2010 at 01:48:25PM -0700, Epshteyn, Eugene wrote:
> Hi Greg,
> 
> Mark asked me to post the patches for him.

Then say that :)

And why would Mark need someone else to do that?

> These patches are on 2.6.34 with the 0415 next patch.

Then say that :)

> We were hoping to get more comments from people to add to TODO list,
> so that the vendor can plan their work to fix the issues and make the
> driver more acceptable to the community.

Isn't Intel the "vendor" here?  If not, why not have them directly
interact with us, you do not want to be put into the middle, it only
slows things down for everyone and is not how Linux kernel development
works.

> The driver already went through some clean-up, but much more work is
> still needed.

Yes, that TODO list is quite large already, fix up all of those and then
ask for more review please.  Reviewing code you know needs lots of work
isn't all that nice to do.

So again, please fix all of that first, get those changes accepted, and
then we can talk :)

thanks,

greg k-h
--
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/