All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Ky Srinivasan <ksrinivasan@novell.com>
Cc: devel@driverdev.osuosl.org,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Virtualization@lists.osdl.org, Zbr@ioremap.net,
	Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [PATCH 4/4] A daemon to gather guest specific information for KVP
Date: Wed, 8 Dec 2010 14:37:00 -0800	[thread overview]
Message-ID: <20101208223700.GA7068@suse.de> (raw)
In-Reply-To: <4CFFA57702000030000918E9@novprvoes0310.provo.novell.com>

How about:
	Subject: [PATCH 4/4] Staging: hv: add userspace daemon code to control key/value connection to the kernel

On Wed, Dec 08, 2010 at 03:34:15PM -0700, Ky Srinivasan wrote:
> >From 718eed47e4c2eb740dc04a6729c8853424ac6965 Mon Sep 17 00:00:00 2001
> From: ksrinivasan <ksrinivasan@novell.com>
> Date: Wed, 8 Dec 2010 14:10:35 -0700
> 
> This daemon gathers all the guest specific information needed to support the
> HyperV KVP functionality. This daemon communicates with the kernel
> component via a netlink channel.
> 
> 
> Signed-off-by: ksrinivasan <ksrinivasan@novell.com>

Wrong name :(


> ---
>  drivers/staging/hv/tools/hv_kvp_daemon.c |  470 ++++++++++++++++++++++++++++++
>  1 files changed, 470 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/staging/hv/tools/hv_kvp_daemon.c
> 
> diff --git a/drivers/staging/hv/tools/hv_kvp_daemon.c b/drivers/staging/hv/tools/hv_kvp_daemon.c
> new file mode 100644
> index 0000000..f5a2dd6
> --- /dev/null
> +++ b/drivers/staging/hv/tools/hv_kvp_daemon.c
> @@ -0,0 +1,470 @@
> +/*
> + * An implementation of key value pair (KVP) functionality for Linux.
> + *
> + *
> + * Copyright (C) 2010, Novell, Inc.
> + * Author : K. Y. Srinivasan <ksrinivasan@novell.com>
> + *
> + * This program is free software; you can redistribute it and/or modify it
> + * under the terms of the GNU General Public License version 2 as published
> + * by the Free Software Foundation.
> + *
> + * This program is distributed in the hope that it will be useful, but
> + * WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, GOOD TITLE or
> + * NON INFRINGEMENT.  See the GNU General Public License for more
> + * details.
> + *
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.

You left in these two paragraphs, which aren't needed.

thanks,

greg k-h

      reply	other threads:[~2010-12-08 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 22:34 [PATCH 4/4] A daemon to gather guest specific information for KVP Ky Srinivasan
2010-12-08 22:37 ` Greg KH [this message]

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=20101208223700.GA7068@suse.de \
    --to=gregkh@suse.de \
    --cc=Virtualization@lists.osdl.org \
    --cc=Zbr@ioremap.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=haiyangz@microsoft.com \
    --cc=ksrinivasan@novell.com \
    --cc=shemminger@vyatta.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 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.