linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Dave Wysochanski <dwysocha@redhat.com>
Cc: dhowells@redhat.com, linux-cachefs@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] netfs: Only call folio_start_fscache() one time for each folio
Date: Fri, 15 Sep 2023 14:31:42 +0100	[thread overview]
Message-ID: <3629819.1694784702@warthog.procyon.org.uk> (raw)
In-Reply-To: <20230608214137.856006-1-dwysocha@redhat.com>

Okay, this looks reasonable.  Should I apply Jeff's suggestion before I send
it to Linus?

David


  parent reply	other threads:[~2023-09-15 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 21:41 [PATCH] netfs: Only call folio_start_fscache() one time for each folio Dave Wysochanski
2023-07-24 14:20 ` [Linux-cachefs] " David Wysochanski
2023-09-11 17:02 ` [PATCH] netfs: Only call folio_start_fscache " Jeff Layton
2023-09-13 11:40   ` Jeff Layton
2023-09-15 13:31 ` David Howells [this message]
2023-09-15 18:41   ` [PATCH] netfs: Only call folio_start_fscache() one " 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=3629819.1694784702@warthog.procyon.org.uk \
    --to=dhowells@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).