From: Ilya Dryomov <idryomov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Ceph fix for 4.8-rc6
Date: Thu, 8 Sep 2016 15:37:00 +0200 [thread overview]
Message-ID: <1473341820-5508-1-git-send-email-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit c6935931c1894ff857616ff8549b61236a19148f:
Linux 4.8-rc5 (2016-09-04 14:31:46 -0700)
are available in the git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-4.8-rc6
for you to fetch changes up to 0f5aa88a7bb28b73253fb42b3df8202142769f39:
ceph: do not modify fi->frag in need_reset_readdir() (2016-09-05 14:30:35 +0200)
----------------------------------------------------------------
A fix for a 4.7 performance regression, caused by a typo in an if
condition.
----------------------------------------------------------------
Nicolas Iooss (1):
ceph: do not modify fi->frag in need_reset_readdir()
fs/ceph/dir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
reply other threads:[~2016-09-08 13:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1473341820-5508-1-git-send-email-idryomov@gmail.com \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).