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 or goto
Date: Wed, 4 Nov 2020 12:02:53 +0100 [thread overview]
Message-ID: <20201104110253.GB1688848@kroah.com> (raw)
In-Reply-To: <20201104105331.16654-1-bernard@vivo.com>
On Wed, Nov 04, 2020 at 02:53:29AM -0800, Bernard Zhao wrote:
> This patch sereies optimise code like:
> {
> case XXX:
> return XXX;
> break; //The break is meanless, so just delete it.
> case YYY:
> goto YYY;
> break; //The break is meanless, so just delete it.
> ......
> }
>
> Signed-off-by: Bernard Zhao <bernard@vivo.com>
>
> ---
> Bernard Zhao (2):
> drivers/tty/nozomi.c: delete no use break after goto
> drivers/tty/serial/imx.c: delete no use break after return
That is not the subject of the patches you sent out, what broke?
next prev parent reply other threads:[~2020-11-04 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 10:53 [PATCH 0/2] drivers/tty: delete break after return or goto Bernard Zhao
2020-11-04 10:53 ` [PATCH 1/2] drivers/tty: delete break after goto Bernard Zhao
2020-11-04 10:53 ` [PATCH 2/2] drivers/tty: delete break after return Bernard Zhao
2020-11-04 11:02 ` Greg Kroah-Hartman [this message]
2020-11-04 11:17 ` Re:Re: [PATCH 0/2] drivers/tty: delete break after return or goto Bernard
2020-11-04 11:59 ` Greg Kroah-Hartman
[not found] ` <AFMA0AACDZrecE*lgOxkLqot.3.1604561695441.Hmail.bernard@vivo.com>
2020-11-05 8:20 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2020-11-07 3:29 Bernard Zhao
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=20201104110253.GB1688848@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