From: Amir Mahdi Ghorbanian <indigoomega021@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: flag specifications for structs
Date: Sat, 28 Dec 2019 10:55:59 -0500 [thread overview]
Message-ID: <20191228155559.GA2115@user-ThinkPad-X230> (raw)
Hello fellow kernel hackers,
I am currently considering tackling the following item
from the TODO list in the drivers/staging/exfat directory:
Fix (thing)->flags to not use magic numbers - multiple
offenders
I am having some difficulty figuring out what the flag bits
of the following two structs, defined in exfat.h, mean:
/* directory structure */
struct chain_t {
u32 dir;
s32 size;
u8 flags;
};
struct file_id_t {
struct chain_t dir;
s32 entry;
u32 type;
u32 attr;
u32 start_clu;
u64 size;
u8 flags;
s64 rwoffset;
s32 hint_last_off;
u32 hint_last_clu;
};
Are the bit specifications defined somewhere in the
linux kernel or online? Any guidance on how to go about figuring
them out would be much appreciated.
next reply other threads:[~2019-12-28 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 15:55 Amir Mahdi Ghorbanian [this message]
2019-12-28 21:24 ` flag specifications for structs Matthew Wilcox
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=20191228155559.GA2115@user-ThinkPad-X230 \
--to=indigoomega021@gmail.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).