From: Bob Peterson <rpeterso@redhat.com>
To: torvalds@linux-foundation.org
Cc: cluster-devel <cluster-devel@redhat.com>, linux-kernel@vger.kernel.org
Subject: GFS2 pull request for this merge window delayed a couple days
Date: Tue, 8 Sep 2015 12:40:21 -0400 (EDT) [thread overview]
Message-ID: <241324676.25202305.1441730421287.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <625755365.25134593.1435330561219.JavaMail.zimbra@redhat.com>
Hi,
I just wanted to give everyone (especially Linus) a heads-up on this.
I've been collecting patches for the GFS2 file system's for-next
branch. The biggest change this time revolves around allowing GFS2
to use rhashtable for its glocks, providing far greater scalability.
Since the patch was posted to cluster-devel, various people (especially
Andreas G) posted a few small correction and cleanup patches. Rather than
giving Linus a big pile of messy patches, I opted to combine them into
one proper patch (doing things "the right way") plus the other five patches
I had already queued. Unfortunately, this was all done just as Stephen
Rothwell sent out his email not to push any more patches to linux-next,
which left me in limbo. I asked Stephen his advice, and based on that,
we decided to:
1. Push the "proper" patch set to for-next today.
2. Give linux-next two days to settle with the six new patches.
3. Then send the formal request to pull the patches for the merge window.
I just wanted to let everyone know why our patch pull request is delayed.
BTW, this six-patch set has already been posted to cluster-devel for
review and been signed off last Wednesday. All of them are pretty much
confined to GFS2 (except for new calls to rhashtable functions) so
hopefully this is just a formality. Sorry for the delay.
Regards,
Bob Peterson
GFS2 Maintainer
prev parent reply other threads:[~2015-09-08 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1946368926.25134466.1435330524247.JavaMail.zimbra@redhat.com>
2015-06-26 14:56 ` GFS2: Pull request (merge window) Bob Peterson
2015-09-08 16:40 ` Bob Peterson [this message]
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=241324676.25202305.1441730421287.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
--cc=cluster-devel@redhat.com \
--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
Powered by JetHome