From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: linux-fsdevel@vger.kernel.org, ext4@vger.kernel.org
Subject: [PATCH 0/3] fs: FS_IOC_FS[GS]ETXATTR promotion
Date: Mon, 4 Jan 2016 16:54:49 +1100 [thread overview]
Message-ID: <1451886892-15548-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
As I mentioned on -fsdevel this morning, the XFS_IOC_FS[SG]SETXATTR
API promotion patch for ext4 project quota really needs to be split
up into two patches: one for the API promotion and the other for
the ext4 implementation of the API.
This short series has the isolated API promotion patch, as well as a
followup cleanup patch in XFS to get rid of the XFS definitions from
the kernel code completely, followed by the first conflicting patch
I had against the ext4-all-in-one patch for a per-inode DAX
enablement flag.
I've pushed these patches out to the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git xfs-setxattr-promotion
And I'll update them and merge them into the for-next branch
according to feedback and review.
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: linux-fsdevel@vger.kernel.org, ext4@vger.kernel.org
Subject: [PATCH 0/3] fs: FS_IOC_FS[GS]ETXATTR promotion
Date: Mon, 4 Jan 2016 16:54:49 +1100 [thread overview]
Message-ID: <1451886892-15548-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
As I mentioned on -fsdevel this morning, the XFS_IOC_FS[SG]SETXATTR
API promotion patch for ext4 project quota really needs to be split
up into two patches: one for the API promotion and the other for
the ext4 implementation of the API.
This short series has the isolated API promotion patch, as well as a
followup cleanup patch in XFS to get rid of the XFS definitions from
the kernel code completely, followed by the first conflicting patch
I had against the ext4-all-in-one patch for a per-inode DAX
enablement flag.
I've pushed these patches out to the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git xfs-setxattr-promotion
And I'll update them and merge them into the for-next branch
according to feedback and review.
Cheers,
Dave.
next reply other threads:[~2016-01-04 5:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 5:54 Dave Chinner [this message]
2016-01-04 5:54 ` [PATCH 0/3] fs: FS_IOC_FS[GS]ETXATTR promotion Dave Chinner
2016-01-04 5:54 ` [PATCH 1/3] fs: XFS_IOC_FS[SG]SETXATTR to FS_IOC_FS[SG]ETXATTR promotion Dave Chinner
2016-01-04 5:54 ` Dave Chinner
2016-01-16 21:22 ` Theodore Ts'o
2016-01-16 21:22 ` Theodore Ts'o
2016-01-04 5:54 ` [PATCH 2/3] xfs: use FS_XFLAG definitions directly Dave Chinner
2016-01-04 5:54 ` Dave Chinner
2016-01-16 21:22 ` Theodore Ts'o
2016-01-16 21:22 ` Theodore Ts'o
2016-01-04 5:54 ` [PATCH 3/3] xfs: introduce per-inode DAX enablement Dave Chinner
2016-01-04 5:54 ` Dave Chinner
2016-01-16 21:22 ` Theodore Ts'o
2016-01-16 21:22 ` Theodore Ts'o
2016-01-21 16:37 ` Dan Williams
2016-01-21 16:37 ` Dan Williams
2016-01-21 21:58 ` Dave Chinner
2016-01-21 21:58 ` Dave Chinner
2016-01-21 22:53 ` Dan Williams
2016-01-21 22:53 ` Dan Williams
2016-01-29 22:20 ` Dave Chinner
2016-01-29 22:20 ` Dave Chinner
2016-01-22 0:45 ` Darrick J. Wong
2016-01-22 0:45 ` Darrick J. Wong
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=1451886892-15548-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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.