From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH v3 1/1] ioctl-fat.2: new manpage for the ioctl fat API
Date: Tue, 03 Feb 2015 19:05:33 +0900 [thread overview]
Message-ID: <87bnlbe2du.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <CAKgNAkh81o6FGY-M5HX5Qt+kk9S8SPW+WcqOZBrA+5PdEn+RGg@mail.gmail.com> (Michael Kerrisk's message of "Tue, 3 Feb 2015 10:54:53 +0100")
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> writes:
> Thanks for the clarification. I have one other question. Currently the
> man page does not document two fields in the __fat_dirent structure:
> d_ino and d_offset. d_ino is presumably the inode number. But, what is
> d_offset?
d_ino and d_off (I guess, d_off you meant) is used only for long
filename part in dirents. And,
d_off == seek offset
d_ino == inode number
same with getdents(), but again it is valid only on long name dirent.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2015-02-03 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKgNAkhuGYKtUKkm2+wU+TwQb6iZ+EmnLDdr4qg4fWHJyL9K5A@mail.gmail.com>
2015-01-23 19:54 ` Heinrich Schuchardt
2015-02-03 8:25 ` Michael Kerrisk (man-pages)
2015-02-03 8:51 ` OGAWA Hirofumi
2015-02-03 9:24 ` Michael Kerrisk (man-pages)
2015-02-03 9:44 ` OGAWA Hirofumi
2015-02-03 9:54 ` Michael Kerrisk (man-pages)
2015-02-03 10:05 ` OGAWA Hirofumi [this message]
2015-02-03 8:49 ` Andreas Dilger
2015-02-03 9:21 ` Michael Kerrisk (man-pages)
2015-02-03 9:48 ` Andreas Dilger
2015-02-03 9:55 ` Michael Kerrisk (man-pages)
2015-02-03 10:10 ` OGAWA Hirofumi
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=87bnlbe2du.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=xypron.glpk@gmx.de \
/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®