From: Josef Bacik <jbacik@fb.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
<dchinner@redhat.com>, <kernel-team@fb.com>
Subject: [GIT PULL] superblock scalability patches
Date: Wed, 19 Aug 2015 10:52:54 -0700 [thread overview]
Message-ID: <55D4C276.2040806@fb.com> (raw)
Hello,
Al would you please consider pulling from
git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
superblock-scaling
I've rebased them onto Linus's master as of a few days ago and retested
them to make sure they were still good to go. They've all been through
a lengthy review process and thoroughly tested. The only change since
the last time I posted the patch series is I've dropped the patch that
created a new writeback list for sync to process because of the new
writeback changes. Porting that patch over is going to take some extra
work and I don't want to hold up the rest of these patches any longer.
Thanks,
Josef
next reply other threads:[~2015-08-19 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 17:52 Josef Bacik [this message]
2015-08-21 22:45 ` [GIT PULL] superblock scalability patches Dave Chinner
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=55D4C276.2040806@fb.com \
--to=jbacik@fb.com \
--cc=dchinner@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.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 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).