From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Bernard Zhao <bernard@vivo.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH] mtd/map: fix typoes for struct memcard
Date: Fri, 2 Oct 2020 09:15:33 +0200 [thread overview]
Message-ID: <20201002071533.26410-1-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20200922112814.26761-1-bernard@vivo.com>
On Tue, 2020-09-22 at 11:28:02 UTC, Bernard Zhao wrote:
> Change struct memcard`s element "removeable" -> "removable".
>
> Signed-off-by: Bernard Zhao <bernard@vivo.com>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next, thanks.
Miquel
prev parent reply other threads:[~2020-10-02 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 11:28 [PATCH] mtd/map: fix typoes for struct memcard Bernard Zhao
2020-10-02 7:15 ` 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=20201002071533.26410-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=bernard@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=opensource.kernel@vivo.com \
--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).