From: Jonathan Corbet <corbet@lwn•net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>
Cc: Linux Doc Mailing List <linux-doc@vger•kernel.org>,
linux-usb@vger•kernel.org, linux-kernel@vger•kernel.org,
codalist@coda•cs.cmu.edu, linux-xfs@vger•kernel.org,
linux-cachefs@redhat•com, linux-fsdevel@vger•kernel.org,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH v3 00/29] Convert files to ReST - part 2
Date: Tue, 5 May 2020 09:28:38 -0600 [thread overview]
Message-ID: <20200505092838.4b1ff075@lwn.net> (raw)
In-Reply-To: <20200428130128.22c4b973@lwn.net>
On Tue, 28 Apr 2020 13:01:28 -0600
Jonathan Corbet <corbet@lwn•net> wrote:
> So I'm happy to merge this set, but there is one thing that worries me a
> bit...
>
> > fs/cachefiles/Kconfig | 4 +-
> > fs/coda/Kconfig | 2 +-
> > fs/configfs/inode.c | 2 +-
> > fs/configfs/item.c | 2 +-
> > fs/fscache/Kconfig | 8 +-
> > fs/fscache/cache.c | 8 +-
> > fs/fscache/cookie.c | 2 +-
> > fs/fscache/object.c | 4 +-
> > fs/fscache/operation.c | 2 +-
> > fs/locks.c | 2 +-
> > include/linux/configfs.h | 2 +-
> > include/linux/fs_context.h | 2 +-
> > include/linux/fscache-cache.h | 4 +-
> > include/linux/fscache.h | 42 +-
> > include/linux/lsm_hooks.h | 2 +-
>
> I'd feel a bit better if I could get an ack or two from filesystem folks
> before I venture that far out of my own yard...what say you all?
It's been another week and nobody has complained, so I'm taking that as
assent; the series has been applied.
Thanks,
jon
prev parent reply other threads:[~2020-05-05 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 21:16 [PATCH v3 00/29] Convert files to ReST - part 2 Mauro Carvalho Chehab
2020-04-27 21:17 ` [PATCH v3 23/29] docs: filesystems: convert spufs/spufs.txt to ReST Mauro Carvalho Chehab
2020-04-28 19:01 ` [PATCH v3 00/29] Convert files to ReST - part 2 Jonathan Corbet
2020-04-28 19:25 ` Jan Harkes
2020-05-05 15:28 ` Jonathan Corbet [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=20200505092838.4b1ff075@lwn.net \
--to=corbet@lwn$(echo .)net \
--cc=codalist@coda$(echo .)cs.cmu.edu \
--cc=linux-cachefs@redhat$(echo .)com \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=linux-xfs@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mchehab+huawei@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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