From: Ingo Molnar <mingo@elte.hu>
To: David Howells <dhowells@redhat.com>
Cc: nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org,
cluster-devel@redhat.com, torvalds@osdl.org,
linux-cachefs@redhat.com, jens.axboe@oracle.com,
linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
linux-cifs-client@lists.samba.org
Subject: Re: [PATCH] SLOW_WORK: Move slow_work's proc file to debugfs
Date: Tue, 1 Dec 2009 17:14:55 +0100 [thread overview]
Message-ID: <20091201161455.GB24897@elte.hu> (raw)
In-Reply-To: <6941.1259681771@redhat.com>
* David Howells <dhowells@redhat.com> wrote:
> Move slow_work's debugging proc file to debugfs.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> ---
>
> Documentation/slow-work.txt | 4 -
> include/linux/slow-work.h | 8 +-
> init/Kconfig | 8 +-
> kernel/Makefile | 2
> kernel/slow-work-debugfs.c | 227 +++++++++++++++++++++++++++++++++++++++++++
> kernel/slow-work-proc.c | 227 -------------------------------------------
> kernel/slow-work.c | 18 ++-
> kernel/slow-work.h | 6 +
> 8 files changed, 253 insertions(+), 247 deletions(-)
> create mode 100644 kernel/slow-work-debugfs.c
> delete mode 100644 kernel/slow-work-proc.c
Nice - thanks for doing this so quickly! It might sound like nitpicking
but /proc ABIs tend to be a lot harder to get rid of than debugfs
interfaces.
Ingo
next prev parent reply other threads:[~2009-12-01 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 15:36 [PATCH] SLOW_WORK: Move slow_work's proc file to debugfs David Howells
2009-12-01 16:14 ` Ingo Molnar [this message]
2009-12-01 16:24 ` Linus Torvalds
2009-12-01 17:11 ` Ingo Molnar
2009-12-01 17:26 ` David Howells
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=20091201161455.GB24897@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=cluster-devel@redhat.com \
--cc=dhowells@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).