public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bernard Zhao <bernard@vivo.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, opensource.kernel@vivo.com
Subject: Re: [PATCH 0/2] drivers/tty: delete break after return
Date: Wed, 4 Nov 2020 07:49:27 +0100	[thread overview]
Message-ID: <20201104064927.GA681413@kroah.com> (raw)
In-Reply-To: <20201104063327.15572-1-bernard@vivo.com>

On Tue, Nov 03, 2020 at 10:33:22PM -0800, Bernard Zhao wrote:
> This patch sereies delete break after return, which will never run.
> 
> Signed-off-by: Bernard Zhao <bernard@vivo.com>
> *** BLURB HERE ***

No blurb?

> 
> Bernard Zhao (2):
>   drivers/tty: delete break after return
>   drivers/tty: delete break after return

You sent different patches, doing different things, yet they have the
same subject lines?  That's not acceptable, sorry.  Please fix up and
resend a new version of this series.

Also, you sent 4 patches, not 2.

thanks,

greg k-h

      parent reply	other threads:[~2020-11-04  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04  6:33 [PATCH 0/2] drivers/tty: delete break after return Bernard Zhao
2020-11-04  6:33 ` [PATCH 1/2] " Bernard Zhao
2020-11-04  6:33 ` [PATCH 2/2] " Bernard Zhao
2020-11-04  6:33 ` [PATCH 0/2] " Bernard Zhao
2020-11-04  6:33 ` [PATCH 1/2] " Bernard Zhao
2020-11-04  6:33 ` [PATCH 2/2] " Bernard Zhao
2020-11-04  6:49 ` Greg Kroah-Hartman [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=20201104064927.GA681413@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bernard@vivo.com \
    --cc=festevam@gmail.com \
    --cc=jirislaby@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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