From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-api@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Cc: ira.weiny@intel.com, Al Viro <viro@zeniv.linux.org.uk>,
Dan Williams <dan.j.williams@intel.com>,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@lst.de>,
"Theodore Y. Ts'o" <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
Jeff Moyer <jmoyer@redhat.com>
Subject: [ANNOUNCE] xfs-linux: vfs-for-next updated to 83d9088659e8
Date: Mon, 4 May 2020 09:13:52 -0700 [thread overview]
Message-ID: <20200504161352.GA13783@magnolia> (raw)
Hi folks,
The vfs-for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
After a very, very long process of discussing how sysadmins and app
programmers are supposed to tag files for DAX data access mode, we have
reached an agreement about how the userspace knobs should work. This
first update contains the necessary documentation updates and statx mode
flag to enable the behaviors that we have decided on. The second part
(hinting at inode eviction to change the DAX mode) will come later after
everyone has had a few days to let this soak in.
The new head of the vfs-for-next branch is commit:
83d9088659e8 Documentation/dax: Update Usage section
New Commits:
Ira Weiny (3):
[efbe3c2493d2] fs: Remove unneeded IS_DAX() check in io_is_direct()
[712b2698e4c0] fs/stat: Define DAX statx attribute
[83d9088659e8] Documentation/dax: Update Usage section
Code Diffstat:
Documentation/filesystems/dax.txt | 142 +++++++++++++++++++++++++++++++++++++-
drivers/block/loop.c | 6 +-
fs/stat.c | 3 +
include/linux/fs.h | 7 +-
include/uapi/linux/stat.h | 1 +
5 files changed, 147 insertions(+), 12 deletions(-)
reply other threads:[~2020-05-04 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200504161352.GA13783@magnolia \
--to=darrick.wong@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--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).