From: Weijie Yuan <wy@wyuan.org>
To: Jiaming Ouyang <jiamingouyang13@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
alexs@kernel.org, corbet@lwn.net,
Dongliang Mu <dzm91@hust.edu.cn>,
si.yanteng@linux.dev, skhan@linuxfoundation.org,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
rdunlap@infradead.org, baikefan@leap-io-kernel.com
Subject: Re: [PATCH v2] docs/zh_CN: add Chinese translation for usb/ohci.rst
Date: Mon, 28 Sep 2026 17:18:16 +0800 [thread overview]
Message-ID: <arow2FPuxMHjFNgb@wyuan.org> (raw)
In-Reply-To: <CAMnqnYwKwb5oTFOXNJyTJk2JEL6bnq+7yENm8v8RnovBYsFVGA@mail.gmail.com>
On 2026-09-28 10:52:04 +0200, Jiaming Ouyang <jiamingouyang13@gmail.com> wrote:
> [PATCH v2] docs/zh_CN: add Chinese translation for usb/ohci.rst
We do not need this [PATCH] line in the email body, because the
"Subject:" header of your email already contains the info.
Or you can refer to my reply to Greg.
> 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.
>
> ---
> Signed-off-by: Jiaming Ouyang <jiamingouyang13@gmail.com>
And your sign-off should be above the three dashes.
so in general like this I guess:
| 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.
|
| Signed-off-by: Jiaming Ouyang <jiamingouyang13@gmail.com>
| ---
| Changes in v2:
| - foo
| - bar
|
| Documentation/translations/zh_CN/usb/ohci.rst | 38 +++++++++++++++++++
| 1 file changed, 38 insertions(+)
| create mode 100644 Documentation/translations/zh_CN/usb/ohci.rst
|
| [...]
Hmm, how about read the SubmittingPatches file before sending out next
version?
https://docs.kernel.org/process/submitting-patches.html#the-canonical-patch-format
Hope it helps.
Thanks.
next prev parent reply other threads:[~2026-09-28 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 8:52 Jiaming Ouyang
2026-09-28 9:01 ` Dongliang Mu
2026-09-28 9:18 ` Weijie Yuan [this message]
2026-09-28 9:34 Jiaming Ouyang
2026-09-28 12:01 ` gregkh
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=arow2FPuxMHjFNgb@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=baikefan@leap-io-kernel.com \
--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®