From: Greg KH <gregkh@suse.de>
To: "Weil, Oren jer" <oren.jer.weil@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"david@woodhou.se" <david@woodhou.se>
Subject: Re: [PATCH 0/7] char/mei: Intel MEI Driver
Date: Wed, 23 Mar 2011 06:50:51 -0700 [thread overview]
Message-ID: <20110323135051.GA16769@suse.de> (raw)
In-Reply-To: <F28B59AD52D84B479DCA469824475335065A96BD7F@hasmsx503.ger.corp.intel.com>
On Wed, Mar 23, 2011 at 02:25:18PM +0200, Weil, Oren jer wrote:
>
> >Are you wanting this version reviewed for inclusion in .40? If you don't
> >feel
> >the code is ready for the main kernel tree, do you want it in staging for the
> >.40
> >release?
>
> Yes, we would like this version to be reviewed for .40.
> I feel that the driver is ready for main kernel tree, but we still working on
> it to make it better.
>
> I don't think we want to put it in staging.
Why not? It needs lots of work, as you have noted, are you going to be
able to get it all cleaned up in the next few weeks properly?
If so, great, I'll wait for your next round of patches to take a look at
them again.
thanks,
greg k-h
next prev parent reply other threads:[~2011-03-23 13:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 10:51 [PATCH 0/7] char/mei: Intel MEI Driver Oren Weil
2011-03-22 10:51 ` [PATCH 1/7] char/mei: PCI device and char driver support Oren Weil
2011-03-22 17:22 ` Arnd Bergmann
2011-03-22 21:57 ` Alan Cox
2011-03-22 22:22 ` Greg KH
2011-03-22 23:04 ` Alan Cox
2011-03-23 7:59 ` Arnd Bergmann
2011-03-22 10:51 ` [PATCH 2/7] char/mei: Interrupt handling Oren Weil
2011-03-22 10:51 ` [PATCH 3/7] char/mei: MEI "Link" layer code - MEI Hardware communications Oren Weil
2011-03-22 10:51 ` [PATCH 4/7] char/mei: MEI driver init flow Oren Weil
2011-03-22 10:51 ` [PATCH 5/7] char/mei: Hardware and MEI driver internal struct definition Oren Weil
2011-03-22 10:51 ` [PATCH 6/7] char/mei: Header file contain the Userland API, (IOCTL and its struct) Oren Weil
2011-03-22 16:26 ` Greg KH
2011-03-22 16:41 ` Arnd Bergmann
2011-03-22 10:51 ` [PATCH 7/7] char/mei: Updates to char/Kconfig ane char/Makefile Oren Weil
2011-03-23 21:43 ` Valdis.Kletnieks
2011-03-22 16:23 ` [PATCH 0/7] char/mei: Intel MEI Driver Greg KH
2011-03-23 12:25 ` Weil, Oren jer
2011-03-23 13:50 ` Greg KH [this message]
2011-03-22 16:50 ` Arnd Bergmann
2011-03-23 7:20 ` Weil, Oren jer
2011-03-23 13:51 ` Greg KH
2011-03-23 15:55 ` Weil, Oren jer
2011-03-23 16:06 ` Greg KH
2011-03-23 16:20 ` Arnd Bergmann
2011-03-24 12:54 ` Weil, Oren jer
2011-03-24 13:10 ` Arnd Bergmann
2011-04-04 15:54 ` Pavel Machek
2011-04-05 6:01 ` Weil, Oren jer
2011-04-18 13:53 ` Pavel Machek
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=20110323135051.GA16769@suse.de \
--to=gregkh@suse.de \
--cc=alan@linux.intel.com \
--cc=david@woodhou.se \
--cc=linux-kernel@vger.kernel.org \
--cc=oren.jer.weil@intel.com \
/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