From: Tim Bird <tim.bird@am.sony.com>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@muc.de>, Roman Zippel <zippel@linux-m68k.org>,
Robert Wisniewski <bob@watson.ibm.com>,
karim@opersys.com
Subject: Re: [PATCH] relayfs redux, part 2
Date: Fri, 28 Jan 2005 12:48:31 -0800 [thread overview]
Message-ID: <41FAA51F.9050304@am.sony.com> (raw)
In-Reply-To: <16890.38062.477373.644205@tut.ibm.com>
Tom Zanussi wrote:
> diff -urpN -X dontdiff linux-2.6.10/fs/Kconfig linux-2.6.10-cur/fs/Kconfig
...
> + This file system is also available as a module ( = code which can be
> + inserted in and removed from the running kernel whenever you want).
> + The module is called relayfs. If you want to compile it as a
> + module, say M here and read <file:Documentation/modules.txt>.
...
This is a real nit, but personally I'd remove the stuff in parens above.
It's not relayfs' job to educate users about what a module is.
I'll try to give some more substantive feedback next week.
Tim
next prev parent reply other threads:[~2005-01-28 20:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 19:38 [PATCH] relayfs redux, part 2 Tom Zanussi
2005-01-28 20:48 ` Tim Bird [this message]
2005-01-28 22:24 ` Andrew Morton
2005-01-29 8:08 ` Andi Kleen
2005-01-30 4:58 ` Tom Zanussi
2005-01-31 12:57 ` Andi Kleen
2005-01-31 16:26 ` Tom Zanussi
2005-01-31 19:41 ` Karim Yaghmour
2005-01-31 21:03 ` Tom Zanussi
2005-01-31 21:12 ` Karim Yaghmour
2005-01-31 19:38 ` Karim Yaghmour
2005-01-29 8:15 ` Greg KH
2005-01-30 5:02 ` Tom Zanussi
2005-01-31 22:10 ` Karim Yaghmour
2005-01-31 22:33 ` Greg KH
2005-01-31 22:35 ` Karim Yaghmour
2005-01-31 23:12 ` Roman Zippel
2005-02-01 15:44 ` Tom Zanussi
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=41FAA51F.9050304@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bob@watson.ibm.com \
--cc=greg@kroah.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@us.ibm.com \
--cc=zippel@linux-m68k.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