From: Tom Zanussi <trz@attbi.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Tom Zanussi <zanussi@us.ibm.com>,
linux-kernel@vger.kernel.org, karim@opersys.com,
bob@watson.ibm.com
Subject: Re: [PATCH] relayfs
Date: Fri, 18 Jul 2003 16:11:25 -0500 [thread overview]
Message-ID: <3F18627D.2040604@attbi.com> (raw)
In-Reply-To: 20030716145508.1742d722.shemminger@osdl.org
Stephen Hemminger wrote:
> Shouldn't relayfs be in the "Pseudo filesystems" part of Kconfig.
> Also don't need the .ko suffix.
>
Yeah, I think that makes more sense. And thanks for your const
filename patch too.
Tom
prev parent reply other threads:[~2003-07-18 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 15:15 [RFC][PATCH 0/5] relayfs Tom Zanussi
2003-07-15 15:27 ` Gianni Tedesco
2003-07-15 16:01 ` Tom Zanussi
2003-07-15 16:40 ` Gianni Tedesco
2003-07-15 17:01 ` Tom Zanussi
2003-07-15 18:45 ` Tom Zanussi
2003-07-16 21:55 ` [PATCH] relayfs Stephen Hemminger
2003-07-16 22:27 ` [PATCH] relay_open const filename Stephen Hemminger
2003-07-18 21:11 ` Tom Zanussi [this message]
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=3F18627D.2040604@attbi.com \
--to=trz@attbi.com \
--cc=bob@watson.ibm.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=zanussi@us.ibm.com \
/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).