From: Dave Chinner <david@fromorbit.com>
To: David Howells <dhowells@redhat.com>
Cc: viro@ZenIV.linux.org.uk, linux-cifs@vger.kernel.org,
linux-nfs@vger.kernel.org, libc-alpha@sourceware.org,
linux-api@vger.kernel.org, andreas.gruenbacher@gmail.com,
samba-technical@lists.samba.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/3] statxat: Provide IOC flags for Windows fs attributes [ver #2]
Date: Fri, 15 Nov 2013 09:11:26 +1100 [thread overview]
Message-ID: <20131114221126.GE11434@dastard> (raw)
In-Reply-To: <20131112184134.2880.9974.stgit@warthog.procyon.org.uk>
On Tue, Nov 12, 2013 at 06:41:35PM +0000, David Howells wrote:
> Provide IOC flags for Windows fs attributes so that they can be retrieved (or
> even altered) using the FS_IOC_[GS]ETFLAGS ioctl and read using statxat().
If you're adding FAT specific flags here into the generic xstat
interface, can we get a bunch of common XFS specific flags into this
interface as well so people don't need to use xfs_io to get/set
them?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2013-11-14 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 18:41 [PATCH 0/3] Extended file stat system call [ver #2] David Howells
2013-11-12 18:41 ` [PATCH 1/3] statxat: Provide IOC flags for Windows fs attributes " David Howells
2013-11-14 22:11 ` Dave Chinner [this message]
[not found] ` <20131112184127.2880.24025.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2013-11-12 18:41 ` [PATCH 2/3] statxat: Add a system call to make extended file stats available " David Howells
[not found] ` <20131112184142.2880.21338.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2013-11-12 22:43 ` Andreas Dilger
2013-11-14 19:19 ` [PATCH 0/3] Extended file stat system call " J. Bruce Fields
2013-11-12 18:41 ` [PATCH 3/3] statxat: AFS: Return enhanced basic attributes " David Howells
2013-11-13 4:15 ` [PATCH 0/3] Extended file stat system call " Carlos O'Donell
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=20131114221126.GE11434@dastard \
--to=david@fromorbit.com \
--cc=andreas.gruenbacher@gmail.com \
--cc=dhowells@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=viro@ZenIV.linux.org.uk \
/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).