mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Sun, 19 Jan 2014 00:46:11 +0100	[thread overview]
Message-ID: <20140118234611.GJ15466@pd.tnic> (raw)
In-Reply-To: <CACPM=kVDpAFSWb3v8zS0+JE2U5C6pSNvqvL+aQ-npLtU05JGrA@mail.gmail.com>

On Sun, Jan 19, 2014 at 12:24:10AM +0100, Bjarke Istrup Pedersen wrote:
> I have submitted a v2 patch - does it look better?

If you mean this:

 include/linux/hyperv.h      | 321 +----------------------------------------
 include/uapi/linux/Kbuild   |   1 +
 include/uapi/linux/hyperv.h | 344 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 347 insertions(+), 319 deletions(-)
 create mode 100644 include/uapi/linux/hyperv.h

you've got the rough idea of uapi headers :-).

Whether that makes sense at all in the hyperv case, you'll have to wait
for the hyperv guys to say something.

What makes me wonder is why do you need to export this now?

Because if those userspace hyperv tools would really need the
definitions in that header, then they never did build before. Which
would be really stupid. Btw, which userspace hyperv tools do you mean?
Where are they?

What am I missing?

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-01-18 23:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18 20:48 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
2014-01-18 23:00           ` Bjarke Istrup Pedersen
2014-01-18 23:24           ` Bjarke Istrup Pedersen
2014-01-18 23:46             ` Borislav Petkov [this message]
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=20140118234611.GJ15466@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®