From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
JFS discussion <jfs-discussion@lists.sourceforge.net>
Subject: [GIT PULL] jfs for 3.11-rc8
Date: Mon, 26 Aug 2013 17:17:39 -0500 [thread overview]
Message-ID: <521BD403.9080905@oracle.com> (raw)
The following changes since commit f1d6e17f540af37bb1891480143669ba7636c4cf:
Merge branch 'akpm' (patches from Andrew Morton) (2013-08-14 10:04:43 -0700)
are available in the git repository at:
git://github.com/kleikamp/linux-shaggy.git tags/jfs-3.11-rc8
for you to fetch changes up to 44512449c0ab368889dd13ae0031fba74ee7e1d2:
jfs: fix readdir cookie incompatibility with NFSv4 (2013-08-15 17:22:29 -0500)
----------------------------------------------------------------
One JFS patch to fix an incompatibility with NFSv4 resulting in the nfs
client reporting a readdir loop.
----------------------------------------------------------------
Dave Kleikamp (1):
jfs: fix readdir cookie incompatibility with NFSv4
fs/jfs/jfs_dtree.c | 31 +++++++++++++++++++++++--------
1 file changed, 23 insertions(+), 8 deletions(-)
reply other threads:[~2013-08-26 22:17 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=521BD403.9080905@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--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