All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Or Idgar <idgar@virtualoco.com>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de, oidgar@redhat.com,
	ghammer@redhat.com, Or Idgar <oridgar@gmail.com>
Subject: Re: [PATCH v2] drivers/virt: vm_gen_counter: initial driver implementation
Date: Sun, 25 Feb 2018 13:47:47 +0100	[thread overview]
Message-ID: <20180225124747.GA592@kroah.com> (raw)
In-Reply-To: <20180225122631.22834-1-idgar@virtualoco.com>

On Sun, Feb 25, 2018 at 02:26:31PM +0200, Or Idgar wrote:
> From: Or Idgar <oridgar@gmail.com>
> 
> This patch is a driver which expose the Virtual Machine Generation ID
> via sysfs. The ID is a UUID value used to differentiate between virtual
> machines.
> 
> The VM-Generation ID is a feature defined by Microsoft (paper:
> http://go.microsoft.com/fwlink/?LinkId=260709) and supported by multiple
> hypervisor vendors.
> 
> Signed-off-by: Or Idgar <oridgar@gmail.com>
> ---
>  Documentation/ABI/testing/sysfs-hypervisor |  13 +++
>  drivers/misc/Kconfig                       |   6 ++
>  drivers/misc/Makefile                      |   1 +
>  drivers/misc/vmgenid.c                     | 140 +++++++++++++++++++++++++++++
>  4 files changed, 160 insertions(+)
>  create mode 100644 Documentation/ABI/testing/sysfs-hypervisor
>  create mode 100644 drivers/misc/vmgenid.c

What changed from v1?  Always put that below the --- line like
Documentation/SubmittingPatches describes how to do.

v3?

thanks,

greg k-h

  reply	other threads:[~2018-02-25 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 12:26 [PATCH v2] drivers/virt: vm_gen_counter: initial driver implementation Or Idgar
2018-02-25 12:47 ` Greg KH [this message]
2018-03-01  9:23 ` kbuild test robot
2018-03-01  9:28 ` kbuild test robot

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=20180225124747.GA592@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=ghammer@redhat.com \
    --cc=idgar@virtualoco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oidgar@redhat.com \
    --cc=oridgar@gmail.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 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.