All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Dave Wysochanski <dwysocha@redhat.com>
Cc: dhowells@redhat.com, Anna Schumaker <anna.schumaker@netapp.com>,
	linux-nfs@vger.kernel.org, linux-cachefs@redhat.com
Subject: Re: [PATCH v2 2/4] NFS: Rename fscache read and write pages functions
Date: Mon, 20 Dec 2021 17:29:48 +0000	[thread overview]
Message-ID: <2512433.1640021388@warthog.procyon.org.uk> (raw)
In-Reply-To: <1639763665-4917-3-git-send-email-dwysocha@redhat.com>

Dave Wysochanski <dwysocha@redhat.com> wrote:

> Rename NFS fscache functions in a more consistent fashion
> to better reflect when we read from and write to fscache.

Do you want me to merge this into my patch that rewrites the nfs cache I/O?

David


  parent reply	other threads:[~2021-12-20 17:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 17:54 [PATCH v2 0/4] Cleanups for NFS fscache and convert from dfprintk to trace events Dave Wysochanski
2021-12-17 17:54 ` [PATCH v2 1/4] NFS: Cleanup usage of nfs_inode in fscache interface and handle i_size properly Dave Wysochanski
2021-12-17 17:54 ` [PATCH v2 2/4] NFS: Rename fscache read and write pages functions Dave Wysochanski
2021-12-17 17:54 ` [PATCH v2 3/4] NFS: Replace dfprintks with tracepoints in fscache read and write page functions Dave Wysochanski
2021-12-17 17:54 ` [PATCH v2 4/4] NFS: Remove remaining dfprintks related to fscache and remove NFSDBG_FSCACHE Dave Wysochanski
2021-12-20 17:29 ` David Howells [this message]
2021-12-20 18:27   ` [PATCH v2 2/4] NFS: Rename fscache read and write pages functions David Wysochanski
2022-01-15 13:50 ` Fwd: [PATCH v2 0/4] Cleanups for NFS fscache and convert from dfprintk to trace events David Wysochanski

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=2512433.1640021388@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=anna.schumaker@netapp.com \
    --cc=dwysocha@redhat.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-nfs@vger.kernel.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.