LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
KY Srinivasan <kys@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 1/1] hyper-v: Replace uuid.h with types.h
Date: Sat, 2 Oct 2021 10:46:16 +0300 [thread overview]
Message-ID: <CAHp75VdXs4QWzeGrLoOEMEcQnC51J-bbsoQTrk+Ju4qL6KgdoA@mail.gmail.com> (raw)
In-Reply-To: <BN8PR21MB1284A4B993EA1C8A51A043C7CAAB9@BN8PR21MB1284.namprd21.prod.outlook.com>
On Sat, Oct 2, 2021 at 1:36 AM Haiyang Zhang <haiyangz@microsoft.com> wrote:
> > -----Original Message-----
> > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Sent: Friday, October 1, 2021 9:56 AM
...
> Hyper-v drivers are using uuid/guid APIs, but they can get the defs from
> linux/mod_devicetable.h:
>
> ./include/linux/mod_devicetable.h:#include <linux/uuid.h>
> ./include/linux/hyperv.h:#include <uapi/linux/hyperv.h>
> ./include/linux/hyperv.h:#include <linux/mod_devicetable.h>
Yes, drivers inside the kernel may use that and this is the correct
way. The uAPI is not using it.
> So your patch looks fine. Thanks.
>
> Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
Thank you!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-10-02 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 13:55 [PATCH v1 1/1] hyper-v: Replace uuid.h with types.h Andy Shevchenko
2021-10-01 22:11 ` Haiyang Zhang
2021-10-02 7:46 ` Andy Shevchenko [this message]
2021-10-06 12:06 ` Wei Liu
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=CAHp75VdXs4QWzeGrLoOEMEcQnC51J-bbsoQTrk+Ju4qL6KgdoA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=decui@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@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 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).