From: Miquel Raynal <miquel.raynal@bootlin.com>
To: dingsenjie@163.com, miquel.raynal@bootlin.com, richard@nod.at,
vigneshr@ti.com
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Ding Senjie <dingsenjie@yulong.com>
Subject: Re: [PATCH v3] mtd: devices: Remove superfluous "break"
Date: Wed, 26 May 2021 11:02:53 +0200 [thread overview]
Message-ID: <20210526090253.180708-1-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20210514124451.20352-1-dingsenjie@163.com>
On Fri, 2021-05-14 at 12:44:51 UTC, dingsenjie@163.com wrote:
> From: Ding Senjie <dingsenjie@yulong.com>
>
> Remove superfluous "break", as there is a "return" before it.
>
> Signed-off-by: Ding Senjie <dingsenjie@yulong.com>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next, thanks.
Miquel
prev parent reply other threads:[~2021-05-26 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 12:44 [PATCH v3] mtd: devices: Remove superfluous "break" dingsenjie
2021-05-26 9:02 ` Miquel Raynal [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=20210526090253.180708-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=dingsenjie@163.com \
--cc=dingsenjie@yulong.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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).