From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] s/driverfs/sysfs/ in include/linux/cpu.h and net/sunrpc/rpc_pipe.c
Date: Fri, 7 Jan 2005 13:58:49 +0100 [thread overview]
Message-ID: <200501071358.51205.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <200501071349.08553.eike-kernel@sf-tec.de>
Hi,
here is another rename of driverfs to sysfs. It looks like there are some
more. I will not fix them all, someone should use "grep -ri drivers *" to
find and fix some more.
Eike
Signed-off-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
--- linux-2.6.10/include/linux/cpu.h 2005-01-01 17:55:38.000000000 +0100
+++ linux-2.6.10/include/linux/cpu.h.fixed 2005-01-07 13:55:36.167681848 +0100
@@ -8,7 +8,7 @@
* Basic handling of the devices is done in drivers/base/cpu.c
* and system devices are handled in drivers/base/sys.c.
*
- * CPUs are exported via driverfs in the class/cpu/devices/
+ * CPUs are exported via sysfs in the class/cpu/devices/
* directory.
*
* Per-cpu interfaces can be implemented using a struct device_interface.
--- linux-2.6.10/net/sunrpc/rpc_pipe.c 2005-01-01 17:55:50.000000000 +0100
+++ linux-2.6.10/net/sunrpc/rpc_pipe.c.fixed 2005-01-07 14:01:05.373634936 +0100
@@ -3,7 +3,7 @@
*
* Userland/kernel interface for rpcauth_gss.
* Code shamelessly plagiarized from fs/nfsd/nfsctl.c
- * and fs/driverfs/inode.c
+ * and fs/sysfs/inode.c
*
* Copyright (c) 2002, Trond Myklebust <trond.myklebust@fys.uio.no>
*
next prev parent reply other threads:[~2005-01-08 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 12:49 [PATCH] s/driverfs/sysfs/ in init/do_mounts.c Rolf Eike Beer
2005-01-07 12:58 ` Rolf Eike Beer [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-27 13:59 [PATCH] s/driverfs/sysfs/ in include/linux/cpu.h and net/sunrpc/rpc_pipe.c Rolf Eike Beer
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=200501071358.51205.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.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.