From: Alex Tomas <alex@clusterfs.com>
To: cmm@us.ibm.com
Cc: Badari Pulavarty <pbadari@gmail.com>,
Martin Michlmayr <tbm@cyrius.com>,
ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Fix section conflict of ext4_ext_{find_goal,invalidate_cache}
Date: Tue, 15 May 2007 23:06:56 +0400 [thread overview]
Message-ID: <464A04D0.80304@clusterfs.com> (raw)
In-Reply-To: <1179255549.4819.7.camel@dyn9047017103.beaverton.ibm.com>
Mingming Cao wrote:
> Don't know. They should all used by ext4 only. Alex, can we remove these
> exported symbols?
yes, I think so.
thanks, Alex
next prev parent reply other threads:[~2007-05-15 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 17:15 Fix section conflict of ext4_ext_{find_goal,invalidate_cache} Martin Michlmayr
2007-05-15 18:09 ` Badari Pulavarty
2007-05-15 18:59 ` Mingming Cao
2007-05-15 19:06 ` Alex Tomas [this message]
2007-05-15 19:08 ` Alex Tomas
2007-05-15 20:43 ` [PATCH] Remove unnecessery exported ext4 symbols Mingming Cao
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=464A04D0.80304@clusterfs.com \
--to=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=tbm@cyrius.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).