From: Weijie Yuan <wy@wyuan.org>
To: 闲逛 <2368492046@qq.com>
Cc: corbet <corbet@lwn.net>, mchehab <mchehab@kernel.org>,
linux-doc <linux-doc@vger.kernel.org>,
skhan <skhan@linuxfoundation.org>,
rdunlap <rdunlap@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] docs: kernel-doc: fix export selection and error handling
Date: Sat, 14 Nov 2026 22:21:04 +0800 [thread overview]
Message-ID: <avhuUH2BLm-EQpPw@wyuan.org> (raw)
In-Reply-To: <tencent_79B4A967C5ADFFCE3CCF0EA9362419ABE105@qq.com>
On Sat, Nov 14, 2026 at 05:05:38PM +0800, 闲逛 wrote:
> Hi Weijie,
>
> Thank you for reviewing my submission, and sorry for the mistakes.
> Although I have been familiar with and using Linux for nearly ten
> years, this is my first time submitting a bug fix to the kernel
> community, and I still have a lot to learn about the process.
Thanks, you're welcome! No need to worry. And sorry if my previous reply
was a bit straightforward. I was a bit out of form this afternoon. :)
Unfortunately, your actual patches of v2 this time were not sent as
replies to the cover letter. Usually, your actual patch, let's say
[2/4], should have a 'In-Reply-To' email header that points to the
Message-ID of your cover letter [0/4]. But now they do not have that
header, therefore not in a thread. See also:
https://docs.kernel.org/process/submitting-patches.html#explicit-in-reply-to-headers
https://docs.kernel.org/translations/zh_CN/process/submitting-patches.html#in-reply-to
If you were using 'git format-patch' and 'git send-email', that should
work well as expected. What did you use to send patches? Is it QQMail
web page? I suspect it would damage the process of sending patches. (But
it seems that your [1/4] can be applied successfully with 'b4 shazam',
so anyway) I had heard before that using QQ email might cause problems,
but I wasn't quite sure either. You may want to take a look at 'git
send-email' or b4.
I'm not familiar with this part, so please wait for others to review.
;-) I suggest that sending out your v3 after receiving some comments,
so you don't need to reroll too often beacause of this format issues.
(But if they want you to tidy it up, that's fine too.)
Yup, the process is not that easy to get familiar with at once. But
please don't be discouraged. If still meet any problems, please feel
free to let me know.
[...]
> Thank you for your time and guidance.
>
> Best regards,
> yuehua-meng
Thanks. The usual practice is to write it as "Yuehua Meng" in your
From and Signed-off-by. But since I can tell that it's a known identity,
I guess it's fine unless later asked. Or perhaps this is just your
original intention. ;-)
Thanks.
prev parent reply other threads:[~2026-11-14 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 5:40 [PATCH " 闲逛
2026-11-14 6:46 ` Weijie Yuan
2026-11-14 9:05 ` [PATCH v2 " 闲逛
2026-11-14 14:21 ` Weijie Yuan [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=avhuUH2BLm-EQpPw@wyuan.org \
--to=wy@wyuan.org \
--cc=2368492046@qq.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.org \
--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®