From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] fs/jbd/journal.c: possible cleanups
Date: Tue, 16 May 2006 12:50:53 -0700 [thread overview]
Message-ID: <20060516125053.03dc1d8f.akpm@osdl.org> (raw)
In-Reply-To: <20060516193956.GS10077@stusta.de>
Adrian Bunk <bunk@stusta.de> wrote:
>
> On Tue, May 16, 2006 at 12:27:31PM -0700, Andrew Morton wrote:
> > Adrian Bunk <bunk@stusta.de> wrote:
> > >
> > > - remove the following unused EXPORT_SYMBOL's:
> > > - journal_set_features
> > > - journal_update_superblock
> >
> > These might be used by lustre - dunno.
>
> I don't see this.
Lustre doesn't use these?
Still, the jbd API is exported for other filesystems to use. If these
functions are considered part of that API (they are) then I'd suggest that
they should be exported.
> > But I'm ducking all patches which alter exports, as usual. If you can get
> > them through the subsystem maintainer then good luck.
> >...
>
> Since you replied to this patch:
> Who is the subsystem maintainer for jbd?
A few people, including me..
next prev parent reply other threads:[~2006-05-16 19:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 17:44 Adrian Bunk
2006-05-16 19:27 ` Andrew Morton
2006-05-16 19:39 ` Adrian Bunk
2006-05-16 19:50 ` Andrew Morton [this message]
2006-05-18 11:52 ` Stephen C. Tweedie
2006-05-16 21:14 ` Theodore Tso
2006-05-16 21:33 ` Adrian Bunk
2006-05-16 22:26 ` [PATCH] Update ext2/ext3/jbd MAINTAINERS entries Theodore Tso
2006-05-18 11:48 ` Stephen C. Tweedie
2006-05-17 1:33 ` [RFC: 2.6 patch] fs/jbd/journal.c: possible cleanups Arjan van de Ven
2006-05-17 1:40 ` Andrew Morton
2006-05-17 1:51 ` Arjan van de Ven
2006-05-17 1:58 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-05-01 7:11 Adrian Bunk
2006-04-23 11:49 Adrian Bunk
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=20060516125053.03dc1d8f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®