From: Greg KH <greg@kroah.com>
To: "Epshteyn, Eugene" <eugene.epshteyn@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/4] Mobile security processor driver
Date: Thu, 29 Apr 2010 14:17:25 -0700 [thread overview]
Message-ID: <20100429211725.GA14909@kroah.com> (raw)
In-Reply-To: <753F67ADE6F5094C9F1DBA00D1BAA8D32551825DAC@orsmsx501.amr.corp.intel.com>
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
next prev parent reply other threads:[~2010-04-30 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 23:10 [RFC PATCH 1/4] Mobile security processor driver Epshteyn, Eugene
2010-04-29 3:36 ` Greg KH
2010-04-29 20:48 ` Epshteyn, Eugene
2010-04-29 21:17 ` Greg KH [this message]
2010-04-29 11:03 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100429211725.GA14909@kroah.com \
--to=greg@kroah.com \
--cc=eugene.epshteyn@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox