From: Christoph Hellwig <hch@infradead.org>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: viro@parcelfarce.linux.theplanet.co.uk,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Patrick Mochel <mochel@digitalimplant.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: RFC: adding an "fs" directory under /sys
Date: Sat, 17 Apr 2004 22:55:09 +0100 [thread overview]
Message-ID: <20040417225509.A21192@infradead.org> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C611302B07C17@lavender-fe.eng.netapp.com>; from Charles.Lever@netapp.com on Sat, Apr 17, 2004 at 02:51:48PM -0700
On Sat, Apr 17, 2004 at 02:51:48PM -0700, Lever, Charles wrote:
> so, i take it you would prefer me to add a kobject to the
> nfs_server struct for my purposes, rather than use the
> unused kobject that is *already* embedded in the
> super_block?
I think Al wants you to understand what you're trying to do first.
Please read up about the kobject lifetime rules first, if you can make
the nfs_server lifetime work with kobjects expectation go for it, but
don't think it's easy.
next prev parent reply other threads:[~2004-04-17 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 21:51 RFC: adding an "fs" directory under /sys Lever, Charles
2004-04-17 21:55 ` Christoph Hellwig [this message]
2004-04-17 22:12 ` viro
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 13:06 Lever, Charles
2004-05-11 17:20 Lever, Charles
2004-05-13 6:18 ` Neil Brown
2004-04-19 13:51 Lever, Charles
2004-05-11 5:54 ` Neil Brown
2004-04-19 13:24 Lever, Charles
2004-04-17 19:46 Lever, Charles
2004-04-17 20:07 ` viro
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=20040417225509.A21192@infradead.org \
--to=hch@infradead.org \
--cc=Charles.Lever@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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).