From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] FYI: GFS2 for-next rebased to 4.15-rc1
Date: Mon, 27 Nov 2017 11:40:56 -0500 (EST) [thread overview]
Message-ID: <874564392.34830960.1511800856324.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <718722640.34830063.1511800627639.JavaMail.zimbra@redhat.com>
Hi,
Linus's merge window is now closed.
I just rebased GFS2's development for-next branch on his new 4.15-rc1
branch. I did this primarily to pick up Jan Kara's patch
"gfs2: use pagevec_lookup_range_tag()" which didn't go through our
tree, aka patch d2bc5b3c67a9cce28616fd90e1651b9c9246fae8
Regards,
Bob Peterson
Red Hat File Systems
parent reply other threads:[~2017-11-27 16:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <718722640.34830063.1511800627639.JavaMail.zimbra@redhat.com>]
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=874564392.34830960.1511800856324.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.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.