linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Yi Jiangshan" <13667453960@163.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: alexandre.belloni@bootlin.com, richard.genoud@gmail.com,
	k2ci <kernel-bot@kylinos.cn>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	jirislaby@kernel.org, claudiu.beznea@microchip.com,
	linux-arm-kernel@lists.infradead.org,
	Jiangshan Yi <yijiangshan@kylinos.cn>
Subject: Re:Re: [PATCH] tty: serial: atmel: fix spelling typo in comment
Date: Thu, 8 Sep 2022 10:24:55 +0800 (CST)	[thread overview]
Message-ID: <d600b6b.e8c.1831aea231e.Coremail.13667453960@163.com> (raw)
In-Reply-To: <YxiP3NfgH+2iIiXy@kroah.com>


At 2022-09-07 20:34:36, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>On Tue, Sep 06, 2022 at 02:39:57PM +0800, Jiangshan Yi wrote:
>> From: Jiangshan Yi <yijiangshan@kylinos.cn>
>> 
>> Fix spelling typo in comment.
>> 
>> Reported-by: k2ci <kernel-bot@kylinos.cn>
>
>What is "k2ci"?

The k2ci is an automated compilation, detection and testing platform built by the company。Just like the kernel test robot built by Intel。
So I write like this:
Reported-by: k2ci <kernel-bot@kylinos.cn>
Refer to the following:
Reported-by: kernel test robot <lkp@intel.com>
Documentation/process/researcher-guidelines.rst

thanks,

Jiangshan Yi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2022-09-08  2:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  6:39 [PATCH] tty: serial: atmel: fix spelling typo in comment Jiangshan Yi
2022-09-06 10:21 ` Richard Genoud
2022-09-07  6:57   ` Claudiu.Beznea
2022-09-07 12:34 ` Greg KH
2022-09-08  2:24   ` Yi Jiangshan [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=d600b6b.e8c.1831aea231e.Coremail.13667453960@163.com \
    --to=13667453960@163.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=kernel-bot@kylinos.cn \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=richard.genoud@gmail.com \
    --cc=yijiangshan@kylinos.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).