From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, Marc Dionne <marc.dionne@auristor.com>,
Christoph Hellwig <hch@lst.de>,
Matthew Wilcox <willy@infradead.org>,
Gaosheng Cui <cuigaosheng1@huawei.com>,
Colin Ian King <colin.i.king@gmail.com>,
linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] afs: A fix, two cleanups and writepage removal
Date: Thu, 22 Dec 2022 11:56:05 +0000 [thread overview]
Message-ID: <2219505.1671710165@warthog.procyon.org.uk> (raw)
Hi Linus,
Could you pull this please? There's a fix for a couple of missing resource
counter decrements, two small cleanups of now-unused bits of code and a
patch to remove writepage support from afs.
Thanks,
David
---
The following changes since commit b6bb9676f2165d518b35ba3bea5f1fcfc0d969bf:
Merge tag 'm68knommu-for-v6.2' of git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu (2022-12-20 08:56:35 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/afs-next-20221222
for you to fetch changes up to a9eb558a5bea66cc43950632f5fffec6b5795233:
afs: Stop implementing ->writepage() (2022-12-22 11:40:35 +0000)
----------------------------------------------------------------
afs next
----------------------------------------------------------------
Colin Ian King (1):
afs: remove variable nr_servers
David Howells (2):
afs: Fix lost servers_outstanding count
afs: Stop implementing ->writepage()
Gaosheng Cui (1):
afs: remove afs_cache_netfs and afs_zap_permits() declarations
fs/afs/dir.c | 1 +
fs/afs/file.c | 3 +-
fs/afs/fs_probe.c | 5 +++-
fs/afs/internal.h | 8 ------
fs/afs/volume.c | 6 +---
fs/afs/write.c | 83 +++++++++++++++++++++++++++++++------------------------
6 files changed, 55 insertions(+), 51 deletions(-)
next reply other threads:[~2022-12-22 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 11:56 David Howells [this message]
2022-12-22 19:28 ` 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=2219505.1671710165@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=colin.i.king@gmail.com \
--cc=cuigaosheng1@huawei.com \
--cc=hch@lst.de \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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®