From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fsnotify changes for v5.5-rc1
Date: Fri, 29 Nov 2019 12:36:51 +0100 [thread overview]
Message-ID: <20191129113651.GD1121@quack2.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify_for_v5.5-rc1
to get three fsnotify cleanups.
Top of the tree is 67e6b4ef8496. The full shortlog is:
Ben Dooks (1):
fsnotify: move declaration of fsnotify_mark_connector_cachep to fsnotify.h
Ben Dooks (Codethink) (1):
fsnotify/fdinfo: exportfs_encode_inode_fh() takes pointer as 4th argument
Jan Kara (1):
fsnotify: Add git tree reference to MAINTAINERS
The diffstat is
MAINTAINERS | 1 +
fs/notify/fdinfo.c | 2 +-
fs/notify/fsnotify.c | 2 --
fs/notify/fsnotify.h | 2 ++
4 files changed, 4 insertions(+), 3 deletions(-)
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2019-11-29 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 11:36 Jan Kara [this message]
2019-11-30 19:40 ` [GIT PULL] fsnotify changes for v5.5-rc1 pr-tracker-bot
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=20191129113651.GD1121@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).