From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [GIT PULL] dtype handling cleanup for v4.21-rc1
Date: Wed, 2 Jan 2019 18:47:36 +0100 [thread overview]
Message-ID: <20190102174736.GB29127@quack2.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git dtype_for_v4.21-rc1
to get a patch to provide generic functions for dtype handling and use those
for ext2. Other filesystems (ext4, btrfs, ocfs2, ...) can then merge the
cleanup patches through their trees.
I've taken the generic functions patch through my tree since Al didn't respond
and it seems non-controversial enough. But I'm sending it separately from my
standard fs fixes batch to mark something unusual is going on (which is also
why I'm sending it so late in the merge window because I forgot about this
topic branch and found out only now).
Top of the tree is 9d6e1fe4e091. The full shortlog is:
Phillip Potter (2):
fs: common implementation of file type
ext2: use common file type conversion
The diffstat is
MAINTAINERS | 1 +
fs/Makefile | 3 +-
fs/ext2/dir.c | 49 +++++++++-------------
fs/fs_types.c | 105 +++++++++++++++++++++++++++++++++++++++++++++++
include/linux/fs.h | 17 +-------
include/linux/fs_types.h | 73 ++++++++++++++++++++++++++++++++
6 files changed, 202 insertions(+), 46 deletions(-)
create mode 100644 fs/fs_types.c
create mode 100644 include/linux/fs_types.h
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2019-01-02 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 17:47 Jan Kara [this message]
2019-01-08 10:05 ` [GIT PULL] dtype handling cleanup for v4.21-rc1 Jan Kara
2019-01-15 9:24 ` Jan Kara
2019-01-15 17:36 ` Linus Torvalds
2019-01-15 18:01 ` Matthew Wilcox
2019-01-15 19:25 ` Linus Torvalds
2019-01-16 12:07 ` Jan Kara
2019-01-16 16:34 ` Phillip Potter
2019-01-16 16:51 ` Jan Kara
2019-01-16 16:56 ` Amir Goldstein
2019-01-17 9:35 ` Jan Kara
2019-01-17 11:17 ` Amir Goldstein
2019-01-16 6:22 ` Amir Goldstein
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=20190102174736.GB29127@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.