From: Ted Ts'o <tytso@mit.edu>
To: Ivan Shmakov <oneingray@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2p_blocks_count () vs. ext2fs_blocks_count ()
Date: Mon, 22 Aug 2011 12:33:29 -0400 [thread overview]
Message-ID: <20110822163329.GC3671@thunk.org> (raw)
In-Reply-To: <864o1at9eo.fsf@gray.siamics.net>
On Mon, Aug 22, 2011 at 10:25:19AM +0700, Ivan Shmakov wrote:
> Apparently, e2p_blocks_count (), a ‘static’ function in
> lib/e2p/ls.c, duplicates the public ext2fs_blocks_count () one
> (lib/ext2fs/blknum.c) as of d4c0d8e5. The same holds for
> e2p_r_blocks_count () and e2p_free_blocks_count ().
>
> The code is, as it seems, exactly the same.
>
> I wonder, isn't there a problem?
That's deliberate; the goal was to make libe2p not dependent on
libext2fs, so that programs such as lsattr don't need to pull in
libext2fs.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-22 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 3:25 e2p_blocks_count () vs. ext2fs_blocks_count () Ivan Shmakov
2011-08-22 16:33 ` Ted Ts'o [this message]
2011-08-22 16:48 ` Ivan Shmakov
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=20110822163329.GC3671@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=oneingray@gmail.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).