From: Jonathan Corbet <corbet@lwn.net>
To: 司延腾 <siyanteng@loongson.cn>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the jc_docs tree
Date: Thu, 21 Jan 2021 11:30:17 -0700 [thread overview]
Message-ID: <20210121113017.62286f45@lwn.net> (raw)
In-Reply-To: <4b5a642b.4d7e.17722b2a4af.Coremail.siyanteng@loongson.cn>
On Thu, 21 Jan 2021 10:07:48 +0800 (GMT+08:00)
司延腾 <siyanteng@loongson.cn> wrote:
> Sorry, I apologize for the inconvenience caused to you, I do not
> quibble, but I have been studying for nearly a week, please pay
> attention to my future patches.
Please don't worry, mistakes happen; we just have to learn from them. I'm
looking forward to your future work.
Thanks,
jon
next prev parent reply other threads:[~2021-01-21 18:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 4:07 linux-next: build warning after merge of the jc_docs tree Stephen Rothwell
2021-01-13 23:27 ` Jonathan Corbet
2021-01-21 2:07 ` 司延腾
2021-01-21 18:30 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 7:28 Stephen Rothwell
2023-12-18 14:18 ` Jonathan Corbet
2023-12-19 23:59 ` Randy Dunlap
2023-12-20 0:02 ` Jonathan Corbet
2023-12-20 0:04 ` Randy Dunlap
2021-02-23 5:19 Stephen Rothwell
2021-01-13 4:14 Stephen Rothwell
2021-01-13 4:12 Stephen Rothwell
2021-01-13 4:18 ` Stephen Rothwell
2020-12-07 7:52 Stephen Rothwell
2020-11-16 6:03 Stephen Rothwell
2020-12-14 19:51 ` Stephen Rothwell
2020-12-14 20:17 ` Jonathan Corbet
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=20210121113017.62286f45@lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=siyanteng@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).