public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: BaiKefan <baikefan@leap-io-kernel.com>
To: Alex Shi <seakeel@gmail.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: si.yanteng@linux.dev, linux-usb@vger.kernel.org,
	alexs@kernel.org, dzm91@hust.edu.cn, corbet@lwn.net,
	linux-doc@vger.kernel.org, doubled@leap-io-kernel.com
Subject: Re: [PATCH v5 0/8] Add Chinese translation for USB subsystem
Date: Thu, 5 Mar 2026 20:19:30 +0800	[thread overview]
Message-ID: <20260305201930.00006c0b@leap-io-kernel.com> (raw)
In-Reply-To: <9e1d404b-2145-481d-930d-c3ba5be0a520@gmail.com>


Hi Greg, Alex,

To clarify, I did send this patchset to the USB subsystem maintainers
in Dec 2025. At that time, I received Greg’s patch-bot auto-reply
noting the tree was closed during the merge window, so no further
review occurred, which made me assume it had been noted but was still
pending.

Per Alex’s suggestion, I will rebase on the latest docs-next, retest,
and resend to the USB maintainers.

Thanks for your guidance and patience.

Best regards,
Kefan


On Thu, 5 Mar 2026 09:36:39 +0800
Alex Shi <seakeel@gmail.com> wrote:

> Hi Baikefan,
> 
> Please rebase the patchset on latest Jon's tree 
> (git://git.lwn.net/linux.git docs-next) and cc to USB maintainers
> with all testing you past.
> 
> Thanks
> Alex
> 
> On 2026/3/4 22:51, Greg KH wrote:
> > On Tue, Mar 03, 2026 at 07:41:05PM +0800, BaiKefan wrote:  
> >> Hi Yanteng and Alexs,
> >>
> >> A few months ago, I submitted a patch for the Chinese translation
> >> of the USB documentation.
> >>
> >> Following your suggestion, I forwarded it to the USB subsystem
> >> maintainer for further review, but I haven’t received any response
> >> yet.  
> > I do not see the forward to the USB subsystem maintainer, where did
> > that happen?
> > 
> > thanks,
> > 
> > greg k-h  
> 
> 
> 


      reply	other threads:[~2026-03-05 12:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  9:25 [PATCH v5 0/8] Add Chinese translation for USB subsystem Kefan Bai
2025-12-08  9:25 ` [PATCH v5 1/8] docs/zh_CN: Add index.rst translation Kefan Bai
2025-12-09  1:41   ` Yanteng Si
2025-12-08  9:25 ` [PATCH v5 2/8] docs/zh_CN: Add acm.rst translation Kefan Bai
2025-12-08  9:25 ` [PATCH v5 3/8] docs/zh_CN: Add authorization.rst translation Kefan Bai
2025-12-08  9:25 ` [PATCH v5 4/8] docs/zh_CN: Add chipidea.rst translation Kefan Bai
2025-12-08  9:25 ` [PATCH v5 5/8] docs/zh_CN: Add dwc3.rst translation Kefan Bai
2025-12-08  9:25 ` [PATCH v5 6/8] docs/zh_CN: Add ehci.rst translation Kefan Bai
2025-12-08  9:25 ` [PATCH v5 7/8] docs/zh_CN: Add usbmon.rst translation Kefan Bai
2025-12-08  9:25 ` [PATCH v5 8/8] docs/zh_CN: Add CREDITS translation Kefan Bai
2025-12-23 13:39 ` [PATCH v5 0/8] Add Chinese translation for USB subsystem Alex Shi
2026-01-04 11:46   ` BaiKefan
2026-03-03 11:41 ` BaiKefan
2026-03-04 14:51   ` Greg KH
2026-03-05  1:36     ` Alex Shi
2026-03-05 12:19       ` BaiKefan [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=20260305201930.00006c0b@leap-io-kernel.com \
    --to=baikefan@leap-io-kernel.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=doubled@leap-io-kernel.com \
    --cc=dzm91@hust.edu.cn \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=seakeel@gmail.com \
    --cc=si.yanteng@linux.dev \
    /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