All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42986] ext2_fs.h requires undefined type umode_t
Date: Tue, 27 Mar 2012 05:02:37 GMT	[thread overview]
Message-ID: <201203270502.q2R52b3I030937@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42986-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42986





--- Comment #7 from Theodore Tso <tytso@mit.edu>  2012-03-27 05:02:37 ---
Which EXT2_IOC_* constants are you using?   Aside from the largely specialized
and as far as I know, not ever used, EXT2_IOC_GETRSVSZ and EXT3_IOC_SETRSVSZ,
you can also use (and in fact are encouraged to use), the generic FS_IOC_*
ioctls instead:

#define    EXT2_IOC_GETFLAGS        FS_IOC_GETFLAGS
#define    EXT2_IOC_SETFLAGS        FS_IOC_SETFLAGS
#define    EXT2_IOC_GETVERSION        FS_IOC_GETVERSION
#define    EXT2_IOC_SETVERSION        FS_IOC_SETVERSION

These ioctl started out as ext2 specific, but they are used by multiple file
systems.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-03-27  5:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 13:23 [Bug 42986] New: ext2_fs.h requires undefined type umode_t bugzilla-daemon
2012-03-24 14:04 ` [Bug 42986] " bugzilla-daemon
2012-03-24 14:16 ` bugzilla-daemon
2012-03-25  1:20 ` bugzilla-daemon
2012-03-25  2:47 ` bugzilla-daemon
2012-03-25 17:21 ` bugzilla-daemon
2012-03-27  4:41 ` bugzilla-daemon
2012-03-27  5:02 ` bugzilla-daemon [this message]
2012-03-27  5:33 ` bugzilla-daemon
2012-03-27  7:31   ` Christoph Hellwig
2012-03-27  5:58 ` bugzilla-daemon
2012-03-27  6:05 ` bugzilla-daemon
2012-03-27  6:17 ` bugzilla-daemon
2012-03-27  6:21 ` bugzilla-daemon
2012-04-12 11:37 ` bugzilla-daemon
2012-04-12 15:04 ` bugzilla-daemon
2012-04-13  6:48 ` bugzilla-daemon

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=201203270502.q2R52b3I030937@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.