linux-kernel - Re: [PATCH] Documentation for sysfs attributes for 3.3 (xen related)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4EC6AADA.2040805@xenotime.net>
Date:	Fri, 18 Nov 2011 10:58:34 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Greg KH <gregkh@...e.de>
CC:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation for sysfs attributes for 3.3 (xen related)

On 11/18/2011 10:33 AM, Greg KH wrote:
> 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?

Well, you are the person who usually tells people that they need
to provide Documentation/ABI/ patches for sysfs files AFAICT.

> 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.

Sounds good.  Thanks.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/