virtualization.lists.linux-foundation.org archive mirror
 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 1/3]: An implementation of HyperV KVP functionality
Date: Tue, 7 Dec 2010 15:10:42 -0800	[thread overview]
Message-ID: <20101207231042.GD27918@suse.de> (raw)
In-Reply-To: <4CFE4E40020000300009170B@novprvoes0310.provo.novell.com>

On Tue, Dec 07, 2010 at 03:09:52PM -0700, Ky Srinivasan wrote:
> This patch is re-based on the latest linux-next tree.
> 
> From: K. Y. Srinivasan <ksrinivasan@novell.com>
> Subject: Reserve a connector index for implementing HyperV Key Value Pair
> (KVP) functionality.

A hint, this is not how you submit a patch.  Please put the Subject line
up above in the real Subject for the email.

Also provide a bit of a description in the body of the email that
explains what is going on.

> 
> Signed-off-by: K. Y. Srinivasan <ksrinivasan@novell.com>
> 
> Index: linux.trees.git/include/linux/connector.h
> ===================================================================

What are these lines from?  Surely you aren't using cvs these days, are
you?

I should be able to take the email and directly feed it to 'git am' to
apply it, without editing it at all.

Care to fix this, and address the connector issues, and then resend them
all?

thanks,

greg k-h

  reply	other threads:[~2010-12-07 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 22:09 [PATCH 1/3]: An implementation of HyperV KVP functionality Ky Srinivasan
2010-12-07 23:10 ` Greg KH [this message]
2010-12-08 21:31   ` Ky Srinivasan
2010-12-08 21:44     ` Evgeniy Polyakov
  -- strict thread matches above, loose matches on Subject: below --
2010-11-22 20:21 Ky Srinivasan

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=20101207231042.GD27918@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).