From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>, baihaowen@meizu.com
Cc: alexs@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, seakeel@gmail.com,
siyanteng01@gmail.com, siyanteng@loongson.cn
Subject: Re: [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion
Date: Sat, 23 Apr 2022 23:24:34 -0600 [thread overview]
Message-ID: <878rrvyrxp.fsf@meer.lwn.net> (raw)
In-Reply-To: <3ce4feb9-5477-e7fb-e98c-3d6342ddc7b5@gmail.com>
Akira Yokosawa <akiyks@gmail.com> writes:
> This patch looks like against akpm's tree (or linux-next).
> So it is not applicable to docs-next of Jonathan's tree at the
> moment.
>
> You need to wait until docs-next catches up akpm's tree.
The alternative is to send the fix to the same maintainer who accepted
the work being changed; that will usually lead to better (and quicker)
results.
Thanks,
jon
next prev parent reply other threads:[~2022-04-24 5:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 1:30 [PATCH V3] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst 司延腾
2022-04-15 2:09 ` yanteng si
2022-04-18 1:58 ` yanteng si
2022-04-18 9:28 ` [PATCH V4] " Haowen Bai
2022-04-18 12:41 ` Alex Shi
2022-04-19 1:23 ` Haowen Bai
2022-04-19 1:46 ` yanteng si
2022-04-19 2:07 ` [PATCH V5] " Haowen Bai
2022-04-19 2:33 ` yanteng si
2022-04-19 3:24 ` baihaowen
2022-04-19 3:34 ` [PATCH V6] " Haowen Bai
2022-04-19 4:27 ` [PATCH V5] " Alex Shi
2022-04-19 5:49 ` [PATCH V7] " Haowen Bai
2022-04-19 7:34 ` [PATCH V8] " Haowen Bai
2022-04-19 14:42 ` yanteng si
2022-04-20 3:06 ` [PATCH 0/2] " Haowen Bai
2022-04-20 3:06 ` [PATCH 1/2] docs/zh_CN: " Haowen Bai
2022-04-23 10:27 ` Alex Shi
2022-04-24 2:56 ` baihaowen
2022-04-24 3:16 ` Alex Shi
2022-04-25 1:17 ` baihaowen
2022-04-25 3:19 ` yanteng si
2022-04-25 8:18 ` baihaowen
2022-04-26 6:57 ` yanteng si
2022-04-26 8:20 ` Alex Shi
2022-04-26 8:23 ` baihaowen
[not found] ` <3f93bb0d-5658-f269-f8cc-d0a964ffb68b@gmail.com>
2022-04-26 8:30 ` baihaowen
2022-04-20 3:06 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
2022-04-20 12:31 ` Bagas Sanjaya
2022-04-20 12:46 ` Jonathan Corbet
2022-04-24 3:38 ` Akira Yokosawa
2022-04-24 5:24 ` Jonathan Corbet [this message]
2022-04-26 8:39 ` Alex Shi
2022-04-21 12:26 ` [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst yanteng si
2022-04-22 1:40 ` baihaowen
2022-04-22 2:35 ` Akira Yokosawa
2022-04-19 1:24 ` [PATCH V4] docs/zh_CN: " baihaowen
2022-04-18 9:29 ` [PATCH V3] " baihaowen
2022-04-25 7:32 [PATCH 0/2] " Haowen Bai
2022-04-25 7:32 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
[not found] <1650956694-30699-1-git-send-email-baihaowen@meizu.com>
2022-04-26 7:04 ` Haowen Bai
2022-04-26 7:07 [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst Haowen Bai
2022-04-26 7:07 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
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=878rrvyrxp.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=alexs@kernel.org \
--cc=baihaowen@meizu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seakeel@gmail.com \
--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).