From: David Miller <davem@davemloft.net>
To: andriy.shevchenko@linux.intel.com
Cc: haiyangz@microsoft.com, kys@microsoft.com,
sthemmin@microsoft.com, sashal@kernel.org,
linux-hyperv@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v1] hv_sock: Use consistent types for UUIDs
Date: Tue, 23 Jul 2019 13:58:52 -0700 (PDT) [thread overview]
Message-ID: <20190723.135852.749823613047584607.davem@davemloft.net> (raw)
In-Reply-To: <20190723163943.65991-1-andriy.shevchenko@linux.intel.com>
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Tue, 23 Jul 2019 19:39:43 +0300
> The rest of Hyper-V code is using new types for UUID handling.
> Convert hv_sock as well.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Applied to net-next.
prev parent reply other threads:[~2019-07-23 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 16:39 [PATCH v1] hv_sock: Use consistent types for UUIDs Andy Shevchenko
2019-07-23 16:57 ` Dexuan Cui
2019-07-23 20:58 ` David Miller [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=20190723.135852.749823613047584607.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.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).