From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Deming Wang <wangdeming@inspur.com>,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Bo Liu <liubo03@inspur.com>
Subject: Re: [PATCH] mtd: sm_ftl: Fix typos in comments
Date: Thu, 22 Jun 2023 23:14:25 +0200 [thread overview]
Message-ID: <20230622211427.3581437-1-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20230621020331.1508-1-wangdeming@inspur.com>
On Wed, 2023-06-21 at 02:03:31 UTC, Deming Wang wrote:
> From: Bo Liu <liubo03@inspur.com>
>
> Fix typo in the description of the 'succesfull'.
>
> Signed-off-by: Bo Liu <liubo03@inspur.com>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next, thanks.
Miquel
next prev parent reply other threads:[~2023-06-22 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 2:03 [PATCH] mtd: sm_ftl: Fix typos in comments Deming Wang
2023-06-22 21:14 ` Miquel Raynal [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-21 1:52 Deming Wang
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=20230622211427.3581437-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=liubo03@inspur.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=wangdeming@inspur.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).