From: Greg KH <gregkh@suse.de>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Hank Janssen <hjanssen@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tom Hanrahan <hanrahat@microsoft.com>
Subject: Re: [patch] Staging: hv: Add new tasks to the TODO file
Date: Thu, 10 Sep 2009 14:00:47 -0700 [thread overview]
Message-ID: <20090910210046.GC3376@suse.de> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF720B8E1E77@TK5EX14MBXC130.redmond.corp.microsoft.com>
On Thu, Sep 10, 2009 at 08:49:56PM +0000, Haiyang Zhang wrote:
> From: Haiyang Zhang <haiyangz@microsoft.com>
>
> Add new tasks to the TODO file.
>
> Cc: Hank Janssen <hjanssen@microsoft.com>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
>
> ---
> diff --git a/drivers/staging/hv/TODO b/drivers/staging/hv/TODO
> index fc754ab..345a59f 100644
> --- a/drivers/staging/hv/TODO
> +++ b/drivers/staging/hv/TODO
> @@ -11,6 +11,12 @@ TODO:
> - audit the network driver
> - audit the block driver
> - audit the scsi driver
> + - SMP Support
> + - Remote Shutdown
> + - Networking . Jumbo Frames
> + - Hot swappable storage devices
> + - Time Synchronization
> + - Key Value Pair Exchange
No, sorry, I'm not going to take this.
The TODO file is for what needs to be done to the code in order to get
it _out_ of the staging tree. Not new features. This should be a list
of things that people can help you out with, which none of these are,
given the lack of documentation on how adding this to the code is able
to be done.
So please, work on removing the items on the TODO list, that way the
code can then be merged into the main portion of the kernel tree. Then
you can go and add new features. There's lots that still needs to be
done with this code before you can think about adding anything new.
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-10 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 20:49 [patch] Staging: hv: Add new tasks to the TODO file Haiyang Zhang
2009-09-10 21:00 ` Greg KH [this message]
2009-09-10 21:12 ` Tom Hanrahan
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=20090910210046.GC3376@suse.de \
--to=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hanrahat@microsoft.com \
--cc=hjanssen@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.