All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-cachefs@redhat.com,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-afs@lists.infradead.org
Subject: Re: [PATCH net-next 00/12] fscache: Fixes, traces and development
Date: Fri, 6 Apr 2018 12:40:19 -0700	[thread overview]
Message-ID: <CA+55aFxtYFbrt8=5tv5O8Ac-8JTcJMxUTZsOBsXcpoU-FBRVNA@mail.gmail.com> (raw)
In-Reply-To: <12717.1523042908@warthog.procyon.org.uk>

On Fri, Apr 6, 2018 at 12:28 PM, David Howells <dhowells@redhat.com> wrote:
>
> That's okay with all the patches as follow up emails?

Actually, I generally just look at the git tree and don't need the
individual patches at all, at least as long as they are only to a
particular subsystem.

So if your git tree only touches fs/afs/ and fs/fscache/, just the
pull request email alone is sufficient.

It's only when people start touching core code or do cross-subsystem
things that I appreciate actually seeing the patches separated out.

In fact, even then it's generally fine to just point to the git tree
and just mention the patches that extend out of just the pure
subsystem (and why they do so).

Both your afs and fscache pulls looked fine to me, and didn't have
that issue (ok, the fscache one touches 9p and afs too, but those are
"afs and 9p use fscache", so it's not something that made me go
"Hmm..".

              Linus

      reply	other threads:[~2018-04-06 19:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 22:06 [PATCH net-next 00/12] fscache: Fixes, traces and development David Howells
2018-04-04 22:06 ` [PATCH 01/12] afs: Invalidate cache on server data change David Howells
2018-04-04 22:06 ` [PATCH 02/12] afs: Use the vnode ID uniquifier in the cache key not the aux data David Howells
2018-04-04 22:07 ` [PATCH 03/12] afs: Be more aggressive in retiring cached vnodes David Howells
2018-04-04 22:07 ` [PATCH 04/12] fscache, cachefiles: Fix checker warnings David Howells
2018-04-04 22:07 ` [PATCH 05/12] fscache: Pass the correct cancelled indications to fscache_op_complete() David Howells
2018-04-04 22:07 ` [PATCH 06/12] fscache: Detect multiple relinquishment of a cookie David Howells
2018-04-04 22:53   ` Linus Torvalds
2018-04-04 22:07 ` [PATCH 07/12] fscache: Fix hanging wait on page discarded by writeback David Howells
2018-04-04 22:07 ` [PATCH 08/12] fscache: Add tracepoints David Howells
2018-04-04 22:07 ` [PATCH 09/12] fscache: Add more tracepoints David Howells
2018-04-04 22:07 ` [PATCH 10/12] fscache: Attach the index key and aux data to the cookie David Howells
2018-04-04 22:07 ` [PATCH 11/12] fscache: Pass object size in rather than calling back for it David Howells
2018-04-04 22:08 ` [PATCH 12/12] fscache: Maintain a catalogue of allocated cookies David Howells
2018-04-04 22:10 ` [PATCH net-next 00/12] fscache: Fixes, traces and development David Howells
2018-04-06 14:44 ` David Howells
2018-04-06 18:21   ` Linus Torvalds
2018-04-06 18:32     ` Linus Torvalds
2018-04-06 21:02       ` Matthew Wilcox
2018-04-06 21:16         ` Linus Torvalds
2018-04-06 19:28     ` David Howells
2018-04-06 19:40       ` Linus Torvalds [this message]

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='CA+55aFxtYFbrt8=5tv5O8Ac-8JTcJMxUTZsOBsXcpoU-FBRVNA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.