mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Jiaming Ouyang <jiamingouyang13@gmail.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	alexs@kernel.org, corbet@lwn.net, skhan@linuxfoundation.org,
	si.yanteng@linux.dev, rdunlap@infradead.org
Subject: Re: [PATCH] docs/zh_CN: add Chinese translation for usb/ohci.rst
Date: Sat, 26 Sep 2026 19:04:35 +0800	[thread overview]
Message-ID: <aremw0r9vCfAvUgM@wyuan.org> (raw)
In-Reply-To: <CAMnqnYwDoNc5=RjEkeRB3-yB+HJvYkrcTBHpPo6cxydSfRMphw@mail.gmail.com>

On 2026-09-26 12:10:16 +0200, Jiaming Ouyang <jiamingouyang13@gmail.com> wrote:

> docs/zh_CN: add Chinese translation for usb/ohci.rst

Besides the comments from Greg, I think the line above should better
belong to the Subject: line in the email headers. But there, it is a part
of email body now, i.e. the line started with 'docs/zh_CN' will appear
twice in the same commit.

Thanks.

> Translate Documentation/usb/ohci.rst into Chinese Simplified.
> 
> The translation covers OHCI driver overview, hardware protocol
> differences (OHCI vs UHCI), improvements since 2.4 kernel,
> queueable interrupt transfers, and non-PCI support.
> 
> ---
> Changes in v2:
> - Correct the date
> - Correct the layout
> - Add specific details for it's contributors
> 
> ---
> Signed-off-by: Jiaming Ouyang <jiamingouyang13@gmail.com>
> ---

  parent reply	other threads:[~2026-09-26 11:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 10:57 Jiaming Ouyang
2026-09-25 12:33 ` Dongliang Mu
2026-09-25 15:28   ` Jiaming Ouyang
2026-09-26  7:13     ` gregkh
2026-09-26 10:10       ` Jiaming Ouyang
2026-09-26 10:18         ` gregkh
2026-09-26 11:04         ` Weijie Yuan [this message]
2026-09-26 11:27       ` Weijie Yuan
  -- strict thread matches above, loose matches on Subject: below --
2026-09-09  6:54 Jiaming Ouyang

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=aremw0r9vCfAvUgM@wyuan.org \
    --to=wy@wyuan.org \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiamingouyang13@gmail.com \
    --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 \
    /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®