From: Greg KH <greg@kroah.com>
To: Oren Weil <oren.jer.weil@intel.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org,
tomas.winkler@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: mei: clean the TODO file from done tasks.
Date: Thu, 22 Sep 2011 09:29:53 -0700 [thread overview]
Message-ID: <20110922162953.GA31282@kroah.com> (raw)
In-Reply-To: <1316612731-20905-2-git-send-email-oren.jer.weil@intel.com>
On Wed, Sep 21, 2011 at 04:45:31PM +0300, Oren Weil wrote:
> Acked-by: Tomas Winkler <tomas.winkler@intel.com>
> Signed-off-by: Oren Weil <oren.jer.weil@intel.com>
> ---
> drivers/staging/mei/TODO | 10 ----------
> 1 files changed, 0 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/staging/mei/TODO b/drivers/staging/mei/TODO
> index 3b6a667..7d9a13b 100644
> --- a/drivers/staging/mei/TODO
> +++ b/drivers/staging/mei/TODO
> @@ -1,14 +1,4 @@
> TODO:
> - - Create in-kernel Client API. Examples of in-kernel clients are watchdog and AMTHI.
Did you really do this?
> - - ME Watchdog Driver to expose standard Linux watchdog interface
And this?
> - - Rewrite AMTHI to use in-kernel client interface
And this?
> - - Cleanup init and probe functions
> - - Review BUG/BUG_ON usage
> - - Cleanup and reorganize header files
> - - Rewrite client data structure
And this?
> - - Make state machine more readable
> - - Add mei.txt with driver explanation and it's driver
You really don't describe the kernel/user api here, that needs to be
well documented as it is a ABI you are creating and we need to know how
it works.
thanks,
greg k-h
next prev parent reply other threads:[~2011-09-22 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 13:45 [PATCH 1/2] staging: mei: Organize the initialization state machine Oren Weil
2011-09-21 13:45 ` [PATCH 2/2] staging: mei: clean the TODO file from done tasks Oren Weil
2011-09-22 16:29 ` Greg KH [this message]
2011-09-22 18:12 ` Winkler, Tomas
2011-09-22 18:31 ` Greg KH
2011-09-22 19:06 ` Winkler, Tomas
2011-09-22 19:38 ` Greg KH
2011-09-22 19:43 ` Greg KH
2011-09-22 19:48 ` Winkler, Tomas
2011-09-22 19:54 ` Greg KH
2011-09-22 20:11 ` Winkler, Tomas
2011-09-22 20:18 ` Greg KH
2011-09-22 21:10 ` Winkler, Tomas
2011-09-22 21:26 ` Greg KH
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=20110922162953.GA31282@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oren.jer.weil@intel.com \
--cc=tomas.winkler@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
Powered by JetHome