From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
<linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
Archit Taneja <architt@codeaurora.org>
Subject: Re: [PATCH] mtd: nand: qcom: fixup whitespace
Date: Fri, 6 May 2016 08:57:49 +0200 [thread overview]
Message-ID: <20160506085749.52fac980@bbrezillon> (raw)
In-Reply-To: <1462477128-105528-1-git-send-email-computersforpeace@gmail.com>
Hi Brian,
On Thu, 5 May 2016 12:38:48 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
> Should be using tabs instead of spaces.
Since I had to rebase to fix the circular dependency problem, I squashed
the changes into "mtd: nand: qcom: switch to mtd_ooblayout_ops".
Thanks,
Boris
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> ---
> Sorry for the resend, I missed linux-mtd the first time...
>
> drivers/mtd/nand/qcom_nandc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/qcom_nandc.c b/drivers/mtd/nand/qcom_nandc.c
> index acd47c1b9c6b..de7d28e62d4e 100644
> --- a/drivers/mtd/nand/qcom_nandc.c
> +++ b/drivers/mtd/nand/qcom_nandc.c
> @@ -1711,7 +1711,7 @@ static void qcom_nandc_select_chip(struct mtd_info *mtd, int chipnr)
> * the sum of the three).
> */
> static int qcom_nand_ooblayout_ecc(struct mtd_info *mtd, int section,
> - struct mtd_oob_region *oobregion)
> + struct mtd_oob_region *oobregion)
> {
> struct nand_chip *chip = mtd_to_nand(mtd);
> struct qcom_nand_host *host = to_qcom_nand_host(chip);
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-06 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 19:38 [PATCH] mtd: nand: qcom: fixup whitespace Brian Norris
2016-05-06 6:57 ` Boris Brezillon [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-05 19:35 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=20160506085749.52fac980@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=architt@codeaurora.org \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).