From: "Rénich Bon Ćirić" <renich@evalinux.com>
To: Weijie Yuan <kernel@wyuan.org>, Dongliang Mu <dzm91@hust.edu.cn>
Cc: "Alex Shi" <alexs@kernel.org>,
"Yanteng Si" <si.yanteng@linux.dev>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"Steffen Klassert" <steffen.klassert@secunet.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rénich Bon Ćirić" <renich@evalinux.com>
Subject: Re: [PATCH] docs/zh_CN: fix stale :Original: reference in xfrm_proc.rst
Date: Wed, 4 Nov 2026 08:58:59 -0600 [thread overview]
Message-ID: <20261104145859.766328-1-renich@evalinux.com> (raw)
In-Reply-To: <autEFEW15g5I0oVT@wyuan.org>
On Wed, Nov 04, 2026 at 10:41:24PM +0800, Weijie Yuan wrote:
> On Wed, Nov 04, 2026 at 10:32:43PM +0800, Dongliang Mu wrote:
> > I have proposed a patchset to revise all the inconsistency between the path
> > of Chinese translation and English documentation and these invalid original
> > fields.
> >
> > Please refer to this patch - [PATCH v3 8/9] docs/zh_CN: update
> > networking/xfrm/xfrm_proc.rst translation
> >
> > https://lore.kernel.org/all/c641a11c-39c8-40c4-b162-10f3a3db57ff@linux.dev/
>
> Ah, I haven't had a chance to look carefully at your series yet. Then
> this patch can be discarded in what's-cooking.
>
> Thanks, both.
Makes complete sense; relocating the translation to match the English
directory layout in Dongliang's v3 8/9 is much cleaner than updating
:Original: in place. Please go ahead and discard my standalone patch.
Thanks for the review and follow-up!
prev parent reply other threads:[~2026-11-04 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 7:31 Rénich Bon Ćirić
2026-11-04 13:42 ` Weijie Yuan
2026-11-04 14:32 ` Dongliang Mu
2026-11-04 14:41 ` Weijie Yuan
2026-11-04 14:46 ` Dongliang Mu
2026-11-04 14:58 ` Weijie Yuan
2026-11-04 15:08 ` Dongliang Mu
2026-11-04 14:58 ` Rénich Bon Ćirić [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=20261104145859.766328-1-renich@evalinux.com \
--to=renich@evalinux.com \
--cc=alexs@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=kernel@wyuan.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=steffen.klassert@secunet.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
all inboxes | Powered by JetHome®