Devicetree
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: liu.qingtao2@zte.com.cn
Cc: krzk@kernel.org, jirislaby@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, marex@nabladev.com,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	alex@ghiti.fr, rdunlap@infradead.org, geert+renesas@glider.be,
	quic_zongjian@quicinc.com, arturs.artamonovs@analog.com,
	robert.marko@sartura.hr, hvilleneuve@dimonoff.com,
	thierry.bultel.yh@bp.renesas.com, julianbraha@gmail.com,
	flavra@baylibre.com, prabhakar.mahadev-lad.rj@bp.renesas.com,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	liu.wenhong35@zte.com.cn, liu.fei16@zte.com.cn,
	dai.hualiang@zte.com.cn, deng.weixian@zte.com.cn,
	jia.yunxiang@zte.com.cn, he.yilin@zte.com.cn, bai.lu5@zte.com.cn,
	yang.susheng@zte.com.cn, shen.lin1@zte.com.cn,
	zuo.jiang@zte.com.cn, hu.shengming@zte.com.cn,
	gao.rui@zte.com.cn, tan.hu@zte.com.cn
Subject: Re: [PATCH v2 0/2] Add ZTE LRX UART driver
Date: Wed, 13 May 2026 12:01:11 +0200	[thread overview]
Message-ID: <2026051341-cattle-multiple-3845@gregkh> (raw)
In-Reply-To: <202605130852.64D8qMgL084414@mse-fl1.zte.com.cn>

On Wed, May 13, 2026 at 04:46:42PM +0800, liu.qingtao2@zte.com.cn wrote:
> >From 9eba3be2e9b4d5c77956258e3c5db95049c3a895 Mon Sep 17 00:00:00 2001
> From: Wenhong Liu
> Date: Mon, 12 May 2026 10:15:55 +0800
> Subject: [PATCH v2 0/2] Add ZTE LRX UART driver

Again, why is this here?

Just use 'git send-email' to send patches out please.  Your patches here
are not threaded together at all and our tooling can not pick them up
:(

thanks,

greg k-h

      reply	other threads:[~2026-05-13 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13  8:46 [PATCH v2 0/2] Add ZTE LRX UART driver liu.qingtao2
2026-05-13 10:01 ` Greg KH [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=2026051341-cattle-multiple-3845@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=arturs.artamonovs@analog.com \
    --cc=bai.lu5@zte.com.cn \
    --cc=conor+dt@kernel.org \
    --cc=dai.hualiang@zte.com.cn \
    --cc=deng.weixian@zte.com.cn \
    --cc=devicetree@vger.kernel.org \
    --cc=flavra@baylibre.com \
    --cc=gao.rui@zte.com.cn \
    --cc=geert+renesas@glider.be \
    --cc=he.yilin@zte.com.cn \
    --cc=hu.shengming@zte.com.cn \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jia.yunxiang@zte.com.cn \
    --cc=jirislaby@kernel.org \
    --cc=julianbraha@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=liu.fei16@zte.com.cn \
    --cc=liu.qingtao2@zte.com.cn \
    --cc=liu.wenhong35@zte.com.cn \
    --cc=marex@nabladev.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=quic_zongjian@quicinc.com \
    --cc=rdunlap@infradead.org \
    --cc=robert.marko@sartura.hr \
    --cc=robh@kernel.org \
    --cc=shen.lin1@zte.com.cn \
    --cc=tan.hu@zte.com.cn \
    --cc=thierry.bultel.yh@bp.renesas.com \
    --cc=yang.susheng@zte.com.cn \
    --cc=zuo.jiang@zte.com.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