From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git - the rest of work.xattr
Date: Wed, 18 May 2016 00:23:00 +0100 [thread overview]
Message-ID: <20160517232300.GM14480@ZenIV.linux.org.uk> (raw)
The rest of work.xattr (non-cifs conversions). There is one difference from
what had been in -next - the commit message of next-to-last commit has
been fixed and the last one had been cherry-picked on top of that. Strictly
speaking, that violates your no-rebases rule, but here all integration testing
remains provably valid - the same sequence of commits, no reordering, the same
trees all along, etc. If that's not acceptable, I can send a truncated
pull request (all but the last two), then send those over email. Up to you...
The following changes since commit ce23e640133484eebc20ca7b7668388213e11327:
->getxattr(): pass dentry and inode as separate arguments (2016-04-11 00:48:00 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
for you to fetch changes up to e0d46f5c6e0ba3a79e64cd60e62b7b7191ed93f3:
btrfs: Switch to generic xattr handlers (2016-05-17 19:17:09 -0400)
----------------------------------------------------------------
Al Viro (1):
gfs2: Switch to generic xattr handlers
Andreas Gruenbacher (6):
ceph: Get rid of d_find_alias in ceph_set_acl
ceph: Switch to generic xattr handlers
jfs: Clean up xattr name mapping
jfs: Switch to generic xattr handlers
ubifs: Switch to generic xattr handlers
btrfs: Switch to generic xattr handlers
Yan, Zheng (1):
ceph: kill __ceph_removexattr()
fs/btrfs/inode.c | 16 ++--
fs/btrfs/xattr.c | 22 +-----
fs/btrfs/xattr.h | 3 -
fs/ceph/acl.c | 14 ++--
fs/ceph/dir.c | 7 +-
fs/ceph/inode.c | 29 ++++---
fs/ceph/super.h | 8 +-
fs/ceph/xattr.c | 192 ++++++---------------------------------------
fs/gfs2/acl.c | 58 +++++++++++---
fs/gfs2/acl.h | 1 +
fs/gfs2/inode.c | 82 +++-----------------
fs/gfs2/xattr.c | 46 +++++++++--
fs/jfs/file.c | 6 +-
fs/jfs/jfs_xattr.h | 6 +-
fs/jfs/namei.c | 6 +-
fs/jfs/symlink.c | 12 +--
fs/jfs/xattr.c | 224 ++++++++++++++++++++---------------------------------
fs/ubifs/dir.c | 6 +-
fs/ubifs/file.c | 12 +--
fs/ubifs/super.c | 1 +
fs/ubifs/ubifs.h | 7 +-
fs/ubifs/xattr.c | 143 ++++++++++++++++------------------
22 files changed, 338 insertions(+), 563 deletions(-)
reply other threads:[~2016-05-17 23:23 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=20160517232300.GM14480@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®