From: Jonathan Corbet <corbet@lwn.net>
To: Yanteng Si <siyanteng01@gmail.com>
Cc: Yanteng Si <siyanteng@loongson.cn>,
chenhuacai@kernel.org, linux-doc@vger.kernel.org,
siyanteng01@gmail.com
Subject: Re: [PATCH 00/11] docs: fix build warning
Date: Mon, 06 Dec 2021 11:09:13 -0700 [thread overview]
Message-ID: <87lf0x38s6.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1638706875.git.siyanteng@loongson.cn>
Yanteng Si <siyanteng01@gmail.com> writes:
> I can't stand these red warnings anymore, especially when I'm testing my
> patches and looking for my own warnings in a sea of warnings. so, let's
> fix them!
So I totally approve of fixing docs build warnings, so thanks for doing
this work. As I was working through the patches, though, I noticed that
these patches are against linux-next, so I can't take them into the docs
tree. Instead, each fix needs to go into the tree that has introduced
the problem.
Thus, I encourage you to separate out this patch set, add an appropriate
Fixes tag to each, then send each separately to the same places where
the original patch went. That should get these problems fixed before
they go into mainline.
Sorry to make more work, but I'd like to see these changes get in. I've
commented on a couple of the individual patches as well.
Thanks,
jon
next prev parent reply other threads:[~2021-12-06 18:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 13:43 [PATCH 00/11] docs: fix build warning Yanteng Si
2021-12-05 13:43 ` [PATCH 01/11] docs/driver-api: Reformatting serial ngsm Yanteng Si
2021-12-06 17:56 ` Jonathan Corbet
2021-12-09 7:05 ` yanteng si
2021-12-05 13:43 ` [PATCH 02/11] docs/admin-guide: Add the necessary blank lines to the writecache Yanteng Si
2021-12-05 13:43 ` [PATCH 03/11] docs/arm64: delete a space from tagged-address-abi Yanteng Si
2021-12-05 13:43 ` [PATCH 04/11] docs/vm: delele three spaces from page_owner Yanteng Si
2021-12-06 17:58 ` Jonathan Corbet
2021-12-09 7:17 ` yanteng si
2021-12-05 13:43 ` [PATCH 05/11] docs/filesystems: add four apostrophes to _start and _len Yanteng Si
2021-12-05 13:43 ` [PATCH 06/11] docs/virt: add a blank line and some - to kvm api Yanteng Si
2021-12-05 13:43 ` [PATCH 07/11] docs/driver-api: Replace a comma in the n_gsm.rst with a double colon Yanteng Si
2021-12-05 13:43 ` [PATCH 08/11] docs/core-api: Replace Footnote Reference in document idr with Substitution Reference Yanteng Si
2021-12-05 13:43 ` [PATCH 09/11] docs/filesystems: fix a label of backend-api Yanteng Si
2021-12-05 13:43 ` [PATCH 10/11] docs/trace: fix a label of boottime-trace Yanteng Si
2021-12-05 13:44 ` [PATCH 11/11] docs/admin-guide: add gpio-aggregator into index Yanteng Si
2021-12-06 18:09 ` Jonathan Corbet [this message]
2021-12-07 11:25 ` [PATCH 00/11] docs: fix build warning yanteng si
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=87lf0x38s6.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=chenhuacai@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
/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).