From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd: nand_bch: fix spelling of "probably"
Date: Fri, 6 May 2016 18:44:44 +0200 [thread overview]
Message-ID: <20160506184444.69e7cc9b@bbrezillon> (raw)
In-Reply-To: <1462552721-93132-1-git-send-email-computersforpeace@gmail.com>
On Fri, 6 May 2016 09:38:41 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Can you take it directly into your tree before preparing your PR for
Linus?
> ---
> drivers/mtd/nand/nand_bch.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/nand_bch.c b/drivers/mtd/nand/nand_bch.c
> index 28ef7b178eac..44763f87eae4 100644
> --- a/drivers/mtd/nand/nand_bch.c
> +++ b/drivers/mtd/nand/nand_bch.c
> @@ -175,7 +175,7 @@ struct nand_bch_control *nand_bch_init(struct mtd_info *mtd)
> * which is called by mtd_ooblayout_count_eccbytes().
> * Make sure they are properly initialized before calling
> * mtd_ooblayout_count_eccbytes().
> - * FIXME: we should probaly rework the sequencing in nand_scan_tail()
> + * FIXME: we should probably rework the sequencing in nand_scan_tail()
> * to avoid setting those fields twice.
> */
> nand->ecc.steps = eccsteps;
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-06 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 16:38 [PATCH] mtd: nand_bch: fix spelling of "probably" Brian Norris
2016-05-06 16:42 ` Brian Norris
2016-05-06 16:44 ` Boris Brezillon [this message]
2016-05-06 16:47 ` Brian Norris
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=20160506184444.69e7cc9b@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).