From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Alexey Dobriyan <adobriyan@gmail.com>,
Daniel Kiss <daniel.kiss@arm.com>,
Yang Shi <yang.shi@linux.alibaba.com>,
Mark Brown <broonie@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
Luigi Semenzato <semenzato@chromium.org>,
Aubrey Li <aubrey.li@linux.intel.com>,
Kees Cook <keescook@chromium.org>, Chao Yu <chao@kernel.org>,
NeilBrown <neilb@suse.de>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] a couple documentation fixes
Date: Wed, 3 Jun 2020 00:38:12 +0200 [thread overview]
Message-ID: <cover.1591137229.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
It follows a couple of fixes for two tables that got broken, probably due to
some conflict between the ReST conversion patches and ungoing updates.
IMO, it would be nice to have those two applied during the merge window,
as they produce a too noisy output.
I have a few more fixes somewhere on my trees, but my plan is to send
you probably after the merge window, as I'm currently busy with some
other stuff (too much work at atomisp side).
Mauro Carvalho Chehab (2):
fs: docs: f2fs.rst: fix a broken table
docs: fs: proc.rst: fix a warning due to a merge conflict
Documentation/filesystems/f2fs.rst | 150 +++++++++++++++++++----------
Documentation/filesystems/proc.rst | 2 +-
2 files changed, 99 insertions(+), 53 deletions(-)
--
2.26.2
next reply other threads:[~2020-06-02 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 22:38 Mauro Carvalho Chehab [this message]
2020-06-02 22:38 ` [PATCH 1/2] fs: docs: f2fs.rst: fix a broken table Mauro Carvalho Chehab
2020-06-08 1:41 ` [f2fs-dev] " Chao Yu
2020-06-02 22:38 ` [PATCH 2/2] docs: fs: proc.rst: fix a warning due to a merge conflict Mauro Carvalho Chehab
2020-06-03 9:54 ` Mark Brown
2020-06-03 19:12 ` Kees Cook
2020-06-19 19:58 ` Jonathan Corbet
2020-06-08 15:20 ` [PATCH 0/2] a couple documentation fixes Jonathan Corbet
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=cover.1591137229.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aubrey.li@linux.intel.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel.kiss@arm.com \
--cc=jaegeuk@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=semenzato@chromium.org \
--cc=tglx@linutronix.de \
--cc=yang.shi@linux.alibaba.com \
/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).