Re: [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

Re: [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

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

Linus Torvalds wrote: > So if you have that [GIT PULL] in the subject line, the pulls will > often be a bit timelier. That's okay with all the patches as follow up emails? David

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

Linus Torvalds wrote: > So if you have that [GIT PULL] in the subject line, the pulls will > often be a bit timelier. That's okay with all the patches as follow up emails? David

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

On Fri, Apr 6, 2018 at 11:21 AM, Linus Torvalds wrote: > > No, but if you can redo the pull request part so that the diffstat I > get will match the diffstat I see in the pull request, that would be > good. Oh, and can you please make sure there is a "[GIT PULL]"

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

On Fri, Apr 6, 2018 at 11:21 AM, Linus Torvalds wrote: > > No, but if you can redo the pull request part so that the diffstat I > get will match the diffstat I see in the pull request, that would be > good. Oh, and can you please make sure there is a "[GIT PULL]" in the subject line for your

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

On Fri, Apr 6, 2018 at 7:44 AM, David Howells wrote: > Hi Linus, > > I've fixed a bug in the final patch that was found by the kbuild test robot > and disabled a debugging statement in an earlier one. This is now tagged as: > >

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

On Fri, Apr 6, 2018 at 7:44 AM, David Howells wrote: > Hi Linus, > > I've fixed a bug in the final patch that was found by the kbuild test robot > and disabled a debugging statement in an earlier one. This is now tagged as: > >

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

Hi Linus, I've fixed a bug in the final patch that was found by the kbuild test robot and disabled a debugging statement in an earlier one. This is now tagged as: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/fscache-next-20180406 Do you want me to

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

Hi Linus, I've fixed a bug in the final patch that was found by the kbuild test robot and disabled a debugging statement in an earlier one. This is now tagged as: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/fscache-next-20180406 Do you want me to

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

> Subject: [PATCH net-next 00/12] fscache: Fixes, traces and development Apologies: that shouldn't say net-next in there. Cut'n'paste error. David

Re: [PATCH net-next 00/12] fscache: Fixes, traces and development

> Subject: [PATCH net-next 00/12] fscache: Fixes, traces and development Apologies: that shouldn't say net-next in there. Cut'n'paste error. David

[PATCH net-next 00/12] fscache: Fixes, traces and development

Hi Linus, Here are some patches that fix some AFS's usage of fscache, two of which conflict with later patches in this series, so I've included them here: (1) Need to invalidate the cache if a foreign data change is detected on the server. (2) Move the vnode ID uniquifier (equivalent to

[PATCH net-next 00/12] fscache: Fixes, traces and development

Hi Linus, Here are some patches that fix some AFS's usage of fscache, two of which conflict with later patches in this series, so I've included them here: (1) Need to invalidate the cache if a foreign data change is detected on the server. (2) Move the vnode ID uniquifier (equivalent to