public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation for sysfs attributes for 3.3 (xen related)
Date: Fri, 18 Nov 2011 10:33:13 -0800	[thread overview]
Message-ID: <20111118183313.GA7417@suse.de> (raw)
In-Reply-To: <4EC6A2D6.10702@xenotime.net>

On Fri, Nov 18, 2011 at 10:24:22AM -0800, Randy Dunlap wrote:
> On 11/18/2011 10:19 AM, Konrad Rzeszutek Wilk wrote:
> > Please accept the following two patches that describe the
> > SysFS of some of the Xen drivers. Thank you.
> > 
> > David Vrabel (2):
> >       xen: document balloon driver sysfs files
> >       xen: document backend sysfs files
> > 
> >  Documentation/ABI/stable/sysfs-bus-xen-backend     |   75 +++++++++++++++++++
> >  .../ABI/stable/sysfs-devices-system-xen_memory     |   77 ++++++++++++++++++++
> >  2 files changed, 152 insertions(+), 0 deletions(-)
> 
> Hey,
> 
> Documentation/ABI/ patches should go to GregKH.

Really?  I'm now in charge of the kernel ABI?

Ah, the power...

/me rubs his hands together

> Greg, can we clarify that in MAINTAINERS ?

Seriously, I'm not in charge of it, that's up to the subsystem for which
the API comes from, I am not the one in charge of the whole thing.

So, for this type of patch, they should go through the xen subsystem
maintainers directly.

thanks,

greg k-h

  reply	other threads:[~2011-11-18 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 18:19 [PATCH] Documentation for sysfs attributes for 3.3 (xen related) Konrad Rzeszutek Wilk
2011-11-18 18:19 ` [PATCH 1/2] xen: document balloon driver sysfs files Konrad Rzeszutek Wilk
2011-11-18 18:19 ` [PATCH 2/2] xen: document backend " Konrad Rzeszutek Wilk
2011-11-18 18:24 ` [PATCH] Documentation for sysfs attributes for 3.3 (xen related) Randy Dunlap
2011-11-18 18:33   ` Greg KH [this message]
2011-11-18 18:56     ` Konrad Rzeszutek Wilk
2011-11-18 18:58     ` Randy Dunlap
2011-11-18 19:10       ` Greg KH

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=20111118183313.GA7417@suse.de \
    --to=gregkh@suse.de \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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