public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
	bbrezillon@kernel.org, marek.vasut@gmail.com, richard@nod.at,
	linux-mtd@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mtd: nand: Kconfig: correct the MTD_NAND_ECC_SW_BCH select
Date: Thu, 18 Apr 2019 18:24:05 +0200	[thread overview]
Message-ID: <20190418182405.67c7fc88@xps13> (raw)
In-Reply-To: <CADYN=9JS9vkw99+LkTVcEQYqwFd1O9_txgRUTYfqK1-9TnKGDg@mail.gmail.com>

Hi Anders,

Anders Roxell <anders.roxell@linaro.org> wrote on Thu, 18 Apr 2019
06:39:06 +0200:

> On Tue, 16 Apr 2019 at 23:53, Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >
> > Hi Anders,
> >
> > Anders Roxell <anders.roxell@linaro.org> wrote on Wed, 10 Apr 2019
> > 21:58:51 +0200:
> >  
> > > Config fragments should not have the prefix 'CONFIG_'.
> > >
> > > Rework to remove the prefix 'CONFIG_' from 'CONFIG_MTD_NAND_ECC_SW_BCH'.
> > >
> > > Fixes: 51ef1d0b2095 ("mtd: nand: Clarify Kconfig entry for software BCH ECC algorithm")
> > > Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> > > ---  
> >
> > Thanks for both patches, do you mind if I squash these with the faulty
> > commits which are still in nand/next?  
> 
> That is fine by me.
> 
> Cheers,
> Anders


Thanks, I squashed this one and applied the second one.

Thanks,
Miquèl

      reply	other threads:[~2019-04-18 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 19:58 [PATCH 1/2] mtd: nand: Kconfig: correct the MTD_NAND_ECC_SW_BCH select Anders Roxell
2019-04-10 19:58 ` [PATCH 2/2] mtd: nand: raw: fix build dependency Anders Roxell
2019-04-16 21:53 ` [PATCH 1/2] mtd: nand: Kconfig: correct the MTD_NAND_ECC_SW_BCH select Miquel Raynal
2019-04-18  4:39   ` Anders Roxell
2019-04-18 16:24     ` 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=20190418182405.67c7fc88@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=anders.roxell@linaro.org \
    --cc=bbrezillon@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --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