From: Borislav Petkov <bp@alien8.de>
To: Bjarke Istrup Pedersen <gurligebis@gentoo.org>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
"K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [PATCH] Adding hyperv.h to uapi headers
Date: Sat, 18 Jan 2014 23:33:08 +0100 [thread overview]
Message-ID: <20140118223308.GH15466@pd.tnic> (raw)
In-Reply-To: <CACPM=kUtm0i5qRWGs9yKBMDZ0fFEQ5-US6wdfa+bjh6ZB2ZhOQ@mail.gmail.com>
On Sat, Jan 18, 2014 at 11:24:53PM +0100, Bjarke Istrup Pedersen wrote:
> I should take all the parts the is not guarded by __KERNEL__, and move
> them to a uapi header, and then include it at the top of the normal
> header. Correct understood? :)
Yes, that's basically the approach but be conservative - export only
stuff which *really* is needed by userspace. And hyperv people should
sanity-check what you're exporting because once it is out, it is cast in
stone and there's no changing.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-01-18 22:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 20:48 [PATCH] Adding hyperv.h to uapi headers Bjarke Istrup Pedersen
2014-01-18 21:06 ` Paul Bolle
2014-01-18 22:07 ` Bjarke Istrup Pedersen
2014-01-18 22:12 ` Borislav Petkov
2014-01-18 22:24 ` Bjarke Istrup Pedersen
2014-01-18 22:33 ` Borislav Petkov [this message]
2014-01-18 23:00 ` Bjarke Istrup Pedersen
2014-01-18 23:24 ` Bjarke Istrup Pedersen
2014-01-18 23:46 ` Borislav Petkov
2014-01-18 23:57 ` Bjarke Istrup Pedersen
2014-01-19 12:20 ` Borislav Petkov
2014-01-19 14:37 ` Bjarke Istrup Pedersen
2014-01-19 14:47 ` Borislav Petkov
2014-01-19 15:29 ` Bjarke Istrup Pedersen
2014-01-19 4:55 ` KY Srinivasan
2014-01-19 10:16 ` Bjarke Istrup Pedersen
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=20140118223308.GH15466@pd.tnic \
--to=bp@alien8.de \
--cc=gurligebis@gentoo.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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.