From: viro@parcelfarce.linux.theplanet.co.uk
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6: why no EXPORT_SYMBOL of get_sb_pseudo()?
Date: Wed, 1 Oct 2003 12:03:03 +0100 [thread overview]
Message-ID: <20031001110303.GQ7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <16250.39070.555465.86772@gargle.gargle.HOWL>
On Wed, Oct 01, 2003 at 11:04:30AM +0200, Mikael Pettersson wrote:
> fs/libfs.c:get_sb_pseudo() isn't exported to modules,
> but a lot of the other stuff in fs/libfs.c is.
>
> Is there a particular reason for this or just an oversight?
>
> Making a private copy of get_sb_pseudo()'s definition works
> in a module, but that's not exactly productive use of
> programmer time or source and object code space.
Are you really sure that get_sb_pseudo() is what you need? It might be
possible, but I suspect that simple_fill_super() would be the right thing
to use. Care to give details?
next prev parent reply other threads:[~2003-10-01 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 9:04 2.6: why no EXPORT_SYMBOL of get_sb_pseudo()? Mikael Pettersson
2003-10-01 11:03 ` viro [this message]
2003-10-01 11:38 ` Mikael Pettersson
2003-10-01 14:41 ` Mikael Pettersson
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=20031001110303.GQ7665@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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