mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT  PULL] Please put NFS client bugfixes for 6.13
Date: Fri, 20 Dec 2024 22:14:04 +0000	[thread overview]
Message-ID: <10d898a194fa59e8f79ba08b24237c01a3f58a80.camel@hammerspace.com> (raw)

Hi Linus,

The following changes since commit 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8:

  Linux 6.13-rc3 (2024-12-15 15:58:23 -0800)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.13-2

for you to fetch changes up to bedb4e6088a886f587d2ea44e0c198c8ce2182c9:

  fs/nfs: fix missing declaration of nfs_idmap_cache_timeout (2024-12-17 11:14:20 -0500)

Thanks,
  Trond
----------------------------------------------------------------
NFS client bugfixes for Linux 6.13

Bugfixes:
- NFS/pnfs: Fix a live lock between recalled layouts and layoutget
- Fix a build warning about an undeclared symbol 'nfs_idmap_cache_timeout'

----------------------------------------------------------------
Trond Myklebust (1):
      NFS/pnfs: Fix a live lock between recalled layouts and layoutget

Zhang Kunbo (1):
      fs/nfs: fix missing declaration of nfs_idmap_cache_timeout

 fs/nfs/pnfs.c  | 2 +-
 fs/nfs/super.c | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



             reply	other threads:[~2024-12-20 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 22:14 Trond Myklebust [this message]
2024-12-21 17:37 ` pr-tracker-bot

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=10d898a194fa59e8f79ba08b24237c01a3f58a80.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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

all inboxes | Powered by JetHome®