linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: KY Srinivasan <kys@microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"apw@canonical.com" <apw@canonical.com>,
	"ben@decadent.org.uk" <ben@decadent.org.uk>
Subject: RE: [PATCH 1/1] Drivers: hv: kvp: Copy the address family information
Date: Tue, 4 Sep 2012 23:36:30 +0000	[thread overview]
Message-ID: <426367E2313C2449837CD2DE46E7EAF9309DFF92@SN2PRD0310MB382.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20120904225655.GA3725@kroah.com>



> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Tuesday, September 04, 2012 6:57 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; devel@linuxdriverproject.org; olaf@aepfle.de;
> apw@canonical.com; ben@decadent.org.uk
> Subject: Re: [PATCH 1/1] Drivers: hv: kvp: Copy the address family information
> 
> On Tue, Sep 04, 2012 at 03:20:19PM -0700, K. Y. Srinivasan wrote:
> > Copy the address family information.
> 
> Why?

This is part of the IP injection protocol in that the host expects this field to reflect what addresses
(address families) are currently bound to the interface. The KVP daemon is currently collecting this 
Information and sending it to the kernel component. I had overlooked copying this and sending it
back to the host. This patch addresses this issue.

Regards,

K. Y





  reply	other threads:[~2012-09-04 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 22:20 [PATCH 1/1] Drivers: hv: kvp: Copy the address family information K. Y. Srinivasan
2012-09-04 22:56 ` Greg KH
2012-09-04 23:36   ` KY Srinivasan [this message]
2012-09-05  0:02     ` Greg KH
2012-09-05  0:29       ` KY Srinivasan
2012-09-05  0:54 K. Y. 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=426367E2313C2449837CD2DE46E7EAF9309DFF92@SN2PRD0310MB382.namprd03.prod.outlook.com \
    --to=kys@microsoft.com \
    --cc=apw@canonical.com \
    --cc=ben@decadent.org.uk \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    /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).