[lkml]   [2018]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH net-next 00/12] fscache: Fixes, traces and development
On Fri, Apr 6, 2018 at 12:28 PM, David Howells <> 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


 \ /
  Last update: 2018-04-06 21:41    [W:0.053 / U:3.380 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site