All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH 1/2] doc, xen: document hypervisor sysfs nodes for xen
Date: Mon, 22 May 2017 16:20:36 +0200	[thread overview]
Message-ID: <b11999f4-f551-40f3-6527-671c96162187__38030.2739482888$1495462898$gmane$org@suse.com> (raw)
In-Reply-To: <41703c16-f2c4-7f35-b445-33bf35ea7f56@oracle.com>

On 22/05/17 15:30, Boris Ostrovsky wrote:
> On 05/22/2017 04:56 AM, Juergen Gross wrote:
>> Today only a few sysfs nodes under /sys/hypervisor/ are documented
>> for Xen in Documentation/ABI/testing/sysfs-hypervisor-pmu. Rename
>> this file to Documentation/ABI/testing/sysfs-hypervisor and add
>> descriptions of the other nodes.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>>  Documentation/ABI/testing/sysfs-hypervisor     | 131 +++++++++++++++++++++++++
>>  Documentation/ABI/testing/sysfs-hypervisor-pmu |  23 -----
>>  MAINTAINERS                                    |   1 +
>>  3 files changed, 132 insertions(+), 23 deletions(-)
>>  create mode 100644 Documentation/ABI/testing/sysfs-hypervisor
>>  delete mode 100644 Documentation/ABI/testing/sysfs-hypervisor-pmu
>>
>> diff --git a/Documentation/ABI/testing/sysfs-hypervisor b/Documentation/ABI/testing/sysfs-hypervisor
> 
> I wonder whether at least some of the non-pmu entries should by now be
> considered stable.

Hmm, do you think the pmu entries are not?

I could:

a) move sysfs-hypervisor as posted here to stable
b) leave the pmu entries in testing and just add another doc for
   the non-pmu entries in stable
c) do some split of the non-pmu entries (which to put where?)
d) or let it all in testing

Next question then: where to put the new guest_type of patch 2?


Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-05-22 14:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22  8:56 [PATCH 0/2] xen: add xen sysfs node Juergen Gross
2017-05-22  8:56 ` [PATCH 1/2] doc, xen: document hypervisor sysfs nodes for xen Juergen Gross
2017-05-22  8:56 ` [PATCH 1/2] doc,xen: " Juergen Gross
2017-05-22 13:30   ` [PATCH 1/2] doc, xen: " Boris Ostrovsky
2017-05-22 13:30   ` [PATCH 1/2] doc,xen: " Boris Ostrovsky
2017-05-22 14:20     ` Juergen Gross
2017-05-22 14:47       ` Boris Ostrovsky
2017-05-22 14:47         ` [PATCH 1/2] doc, xen: " Boris Ostrovsky
2017-05-22 14:20     ` Juergen Gross [this message]
2017-05-22  8:57 ` [PATCH 2/2] xen: add sysfs node for guest type Juergen Gross
2017-05-22 13:17   ` Boris Ostrovsky
2017-05-22 14:21     ` Juergen Gross
2017-05-22 14:21     ` Juergen Gross
2017-05-22 13:17   ` Boris Ostrovsky
2017-05-22 13:33   ` Andrew Cooper
2017-05-22 13:33   ` [Xen-devel] " Andrew Cooper
2017-05-22 14:16     ` Juergen Gross
2017-05-22 14:16     ` Juergen Gross
2017-05-22 14:35     ` [Xen-devel] " Boris Ostrovsky
2017-05-22 14:38       ` Andrew Cooper
2017-05-22 14:38       ` [Xen-devel] " Andrew Cooper
2017-05-22 14:35     ` Boris Ostrovsky
2017-05-22 13:45   ` Jan Beulich
2017-05-22 13:45   ` [Xen-devel] " Jan Beulich
     [not found]   ` <59230794020000780015BC13@suse.com>
2017-05-22 14:20     ` Juergen Gross
2017-05-22 14:20     ` [Xen-devel] " Juergen Gross
2017-05-22 15:23   ` Konrad Rzeszutek Wilk
2017-05-22 15:23   ` [Xen-devel] " Konrad Rzeszutek Wilk
2017-05-22 15:28     ` Juergen Gross
2017-05-22 15:28     ` [Xen-devel] " Juergen Gross
2017-05-22 15:37       ` Jan Beulich
2017-05-22 15:37         ` Jan Beulich
     [not found]       ` <592321E4020000780015BD0E@suse.com>
2017-05-22 15:52         ` [Xen-devel] " Juergen Gross
2017-05-22 15:52         ` Juergen Gross
2017-05-22  8:57 ` Juergen Gross

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='b11999f4-f551-40f3-6527-671c96162187__38030.2739482888$1495462898$gmane$org@suse.com' \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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 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.