From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, geert@linux-m68k.org, willy@infradead.org,
ceph-devel@vger.kernel.org, linux-afs@lists.infradead.org,
linux-cachefs@redhat.com, linux-cifs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: [GIT PULL] netfs: Fixes
Date: Tue, 25 May 2021 14:01:02 +0100 [thread overview]
Message-ID: <4007708.1621947662@warthog.procyon.org.uk> (raw)
Hi Linus,
If you could pull this, there are a couple of fixes to the new netfs lib in
it:
(1) Pass the AOP flags through from netfs_write_begin() into
grab_cache_page_write_begin().
(2) Automatically enable in Kconfig netfs lib rather than presenting an
option for manual enablement.
David
---
The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/netfs-lib-fixes-20200525
for you to fetch changes up to b71c791254ff5e78a124c8949585dccd9e225e06:
netfs: Make CONFIG_NETFS_SUPPORT auto-selected rather than manual (2021-05-25 13:48:04 +0100)
----------------------------------------------------------------
netfslib fixes
----------------------------------------------------------------
David Howells (2):
netfs: Pass flags through to grab_cache_page_write_begin()
netfs: Make CONFIG_NETFS_SUPPORT auto-selected rather than manual
fs/netfs/Kconfig | 2 +-
fs/netfs/read_helper.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2021-05-25 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 13:01 David Howells [this message]
2021-05-25 17:36 ` [GIT PULL] netfs: Fixes pr-tracker-bot
2024-01-25 10:13 [GIT PULL] netfs fixes Christian Brauner
2024-01-25 20:00 ` 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=4007708.1621947662@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=v9fs-developer@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.