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, rdunlap@infradead.org
Subject: Re: [PATCH v3] docs/zh_CN: add Chinese translation for usb/ohci.rst
Date: Sat, 3 Oct 2026 22:24:20 +0800 [thread overview]
Message-ID: <asEQFPeGY46qogz1@wyuan.org> (raw)
In-Reply-To: <CAMnqnYy5Jt-DWtYrjdekr=M=NBvdW+tu340BLf=GXQv-qi2gQw@mail.gmail.com>
On 2026-10-03 15:59:30 +0200, Jiaming Ouyang <jiamingouyang13@gmail.com> wrote:
> 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 v3:
> - Correct the docs list in index.rst
> ---
If you merely want to resend the patch to achieve the effect of a ping,
then please change the title to [PATCH RESEND v3] or similar. And this
is documented in our docs. But generally speaking, this is too early.
And I cannot apply this on the tip of Alex's docs-next now as well:
$ b4 shazam https://lore.kernel.org/linux-doc/CAMnqnYy5Jt-DWtYrjdekr=M=NBvdW+tu340BLf=GXQv-qi2gQw@mail.gmail.com/
Looking up CAMnqnYy5Jt-DWtYrjdekr=M=NBvdW+tu340BLf=GXQv-qi2gQw@mail.gmail.com
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 1 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Analyzing 23 code-review messages
Checking attestation on all messages, may take a moment...
---
✓ [PATCH v3] docs/zh_CN: add Chinese translation for usb/ohci.rst
---
✓ Signed: DKIM/gmail.com
---
Total patches: 1
---
Applying: docs/zh_CN: add Chinese translation for usb/ohci.rst
Patch failed at 0001 docs/zh_CN: add Chinese translation for usb/ohci.rst
error: git diff header lacks filename information when removing 1 leading pathname component at /Volumes/Linux/linux/.git/rebase-apply/patch:11
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
If it's not on me, you might try git-send-email(1) or b4.
Thanks.
next prev parent reply other threads:[~2026-10-03 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 13:59 [PATCH v3] docs/zh_CN: add Chinese translation for usb/ohci.rst Jiaming Ouyang
2026-10-03 14:24 ` Weijie Yuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-01 10: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=asEQFPeGY46qogz1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.