From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bernard <bernard@vivo.com>
Cc: opensource.kernel@vivo.com, linux-serial@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Re: Re: [PATCH 0/2] drivers/tty: delete break after return or goto
Date: Thu, 5 Nov 2020 09:20:54 +0100 [thread overview]
Message-ID: <20201105082054.GA3426404@kroah.com> (raw)
In-Reply-To: <AFMA0AACDZrecE*lgOxkLqot.3.1604561695441.Hmail.bernard@vivo.com>
On Thu, Nov 05, 2020 at 03:34:55PM +0800, Bernard wrote:
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> Date: 2020-11-04 19:59:03
> To: Bernard <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: Re: [PATCH 0/2] drivers/tty: delete break after return or goto>On Wed, Nov 04, 2020 at 07:17:56PM +0800, Bernard wrote:
> >>
> >>
> >> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >> Date: 2020-11-04 19:02:53
> >> 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>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?
> >>
> >> Hi:
> >>
> >> I am sorry that I am a little confused:
> >> The patch series`s subject is "drivers/tty: delete break after return or goto"
> >> and the blurb is:
> >> 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.
> >> ......
> >> }
> >> last, the modified files are:
> >> Bernard Zhao (2):
> >> drivers/tty/nozomi.c: delete no use break after goto
> >> drivers/tty/serial/imx.c: delete no use break after return
> >>
> >> Is there something wrong that I didn`t catch?
> >
> >The above lines do not match up with the subject lines of the patches
> >you sent out, so something went wrong.
>
>
> Hi, Greg:
>
> Sorry to bother you.
> I am a newcomer to the community, and this is my first time submitting a patch series.
You might want to start in the drivers/staging/ part of the kernel to
get your bearings and work out these types of things. It's "easier"
there as the code there needs lots of work and it's set up to handle new
developers like yourself.
> I am sorry that I still don't understand:"The above lines do not match up with the subject lines of the patches you sent out, so something went wrong."
> I compared my patch series with other people`s patch series, as shown in the picture below, they look the seem.
> The only difference is that I made a signature here, so is this the issue that you mean?
the output of the git command that caused those lines to be written was
taken from the subject lines of the patches in your tree. Yet the
subject lines of the patches you emailed us did not match that at all,
so what you sent is not what you actually had here when you generated
that cover letter. So something went wrong with your process.
Try deleting all patch files in the directory and generating them again,
and then emailing the series to yourself to verify that everything
matches up properly.
hope this helps,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-05 8:20 UTC|newest]
Thread overview: 7+ 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 ` [PATCH 0/2] drivers/tty: delete break after return or goto Greg Kroah-Hartman
2020-11-04 11:17 ` 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 [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=20201105082054.GA3426404@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