From: Greg KH <greg@kroah.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: liguozhu@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: Problem with debugfs
Date: Tue, 21 Sep 2010 06:40:27 -0700 [thread overview]
Message-ID: <20100921134027.GA3139@kroah.com> (raw)
In-Reply-To: <20100920213825.72ac1a92.rdunlap@xenotime.net>
On Mon, Sep 20, 2010 at 09:38:25PM -0700, Randy Dunlap wrote:
> On Mon, 20 Sep 2010 20:43:14 -0700 Greg KH wrote:
>
> > On Tue, Sep 21, 2010 at 10:21:12AM +0800, liguozhu@huawei.com wrote:
> > > Hi, there,
> > >
> > > I do not know who is the maintainer for debugfs now.
> >
> > Did it change? It's always been me. I guess I never created a
> > MAINTAINERS entry, is it really needed?
>
>
> We shouldn't assume that everyone uses git and can then use
> ./scripts/get_maintainer.pl.
Good point, I've queued up the following patch to my trees.
thanks,
greg k-h
----------
From: Greg Kroah-Hartman <gregkh@suse.de>
Subject: debugfs: mark me as the maintainer
Add DEBUGFS information to my MAINTAINERS entry as some people have
asked about this recently.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2033,14 +2033,16 @@ F: drivers/block/drbd/
F: lib/lru_cache.c
F: Documentation/blockdev/drbd/
-DRIVER CORE, KOBJECTS, AND SYSFS
+DRIVER CORE, KOBJECTS, DEBUGFS AND SYSFS
M: Greg Kroah-Hartman <gregkh@suse.de>
T: quilt kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
S: Supported
F: Documentation/kobject.txt
F: drivers/base/
F: fs/sysfs/
+F: fs/debugfs/
F: include/linux/kobj*
+F: include/linux/debugfs.h
F: lib/kobj*
DRM DRIVERS
next prev parent reply other threads:[~2010-09-21 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 2:21 Problem with debugfs liguozhu
2010-09-21 3:43 ` Greg KH
2010-09-21 4:38 ` Randy Dunlap
2010-09-21 13:40 ` Greg KH [this message]
2010-09-21 6:13 ` Kenneth
2010-09-21 7:23 ` KOSAKI Motohiro
2010-09-21 7:31 ` Andi Kleen
2010-09-21 8:04 ` Wu Fengguang
2010-09-21 8:12 ` Andi Kleen
2010-09-25 1:18 ` Kenneth
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=20100921134027.GA3139@kroah.com \
--to=greg@kroah.com \
--cc=liguozhu@huawei.com \
--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