From: Greg KH <greg@kroah.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: karim@opersys.com, linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
Roman Zippel <zippel@linux-m68k.org>,
Tom Zanussi <zanussi@us.ibm.com>,
Robert Wisniewski <bob@watson.ibm.com>,
Tim Bird <tim.bird@AM.SONY.COM>
Subject: Re: [PATCH] relayfs redux for 2.6.10: lean and mean
Date: Thu, 20 Jan 2005 23:46:01 -0800 [thread overview]
Message-ID: <20050121074601.GA19550@kroah.com> (raw)
In-Reply-To: <41F0AEEF.8060707@bigpond.net.au>
On Fri, Jan 21, 2005 at 06:27:43PM +1100, Peter Williams wrote:
> Greg KH wrote:
> >On Fri, Jan 21, 2005 at 01:15:28PM +1100, Peter Williams wrote:
> >
> >>Perhaps the logical solution is to implement debugfs in terms of relayfs?
> >
> >
> >What do you mean by this statement?
>
> I mean that if, as you say, debugfs is very similar to relayfs only more
> restricted (i.e. a debugging option) then it should be implementable as
> an instance or specialization of the more general relayfs and that this
> should be a better solution than two independent implementations of
> similar functionality.
Ah.
No.
The implementations are not of the same functionality, or so Karim says.
thanks,
greg k-h
next prev parent reply other threads:[~2005-01-21 7:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 6:23 [PATCH] relayfs redux for 2.6.10: lean and mean Karim Yaghmour
2005-01-20 14:50 ` Greg KH
2005-01-21 1:38 ` Karim Yaghmour
2005-01-21 2:15 ` Peter Williams
2005-01-21 6:39 ` Greg KH
2005-01-21 7:27 ` Peter Williams
2005-01-21 7:46 ` Greg KH [this message]
2005-01-21 6:43 ` Greg KH
2005-01-23 8:07 ` Karim Yaghmour
2005-01-20 15:06 ` Greg KH
2005-01-20 19:51 ` Pekka Enberg
2005-02-07 3:04 ` [PATCH] relayfs crash Kingsley Cheung
2005-02-07 3:16 ` Karim Yaghmour
2005-02-07 4:42 ` Tom Zanussi
2005-02-07 4:47 ` Kingsley Cheung
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=20050121074601.GA19550@kroah.com \
--to=greg@kroah.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bob@watson.ibm.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pwil3058@bigpond.net.au \
--cc=tim.bird@AM.SONY.COM \
--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 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.