From: Max Krummenacher <max.oss.09@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] nand: nand torture: follow sync with linux v4.6
Date: Thu, 09 Jun 2016 23:13:24 +0200 [thread overview]
Message-ID: <1465506804.3826.5.camel@gmail.com> (raw)
In-Reply-To: <1465492215.22191.122.camel@buserror.net>
Am Donnerstag, den 09.06.2016, 12:10 -0500 schrieb Scott Wood:
> On Thu, 2016-06-09 at 10:35 +0200, Max Krummenacher wrote:
> > Hi Scott
> >
> > 2016-06-09 1:47 GMT+02:00 Scott Wood <scott.wood@nxp.com>:
> > > On 06/07/2016 06:47 AM, Max Krummenacher wrote:
> > > > follow parameter name change (nand to mtd) to fix compiler
> > > > error.
> > > >
> > > > Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
> > > >
> > > > ---
> > > >
> > > > Changes in v2:
> > > > - Patch v1 1/1 went into master, but Scott's patch series
> > > > syncing
> > > > with kernel v4.6 introduced an additional compile time error.
> > > >
> > > > drivers/mtd/nand/nand_util.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/drivers/mtd/nand/nand_util.c
> > > > b/drivers/mtd/nand/nand_util.c
> > > > index 5bba66a..e8bcc34 100644
> > > > --- a/drivers/mtd/nand/nand_util.c
> > > > +++ b/drivers/mtd/nand/nand_util.c
> > > > @@ -820,7 +820,7 @@ int nand_torture(struct mtd_info *mtd,
> > > > loff_t
> > > > offset)
> > > > {
> > > > u_char patterns[] = {0xa5, 0x5a, 0x00};
> > > > struct erase_info instr = {
> > > > - .mtd = nand,
> > > > + .mtd = mtd,
> > > > .addr = offset,
> > > > .len = mtd->erasesize,
> > > > };
> > >
> > > This got missed because no boards enable CONFIG_CMD_NAND_TORTURE.
> > > If
> > > you use this option could you enable it in the relevant board?
> >
> > I believe this makes option makes only sense if you do HW bringup
> > or
> > have issues with
> > your NAND driver. (Which I currently have with an i.MX 7 design)
> > So likely one would not want to enable this for production code.
>
> That's why I suggested the alternative of adding one or more targets
> aimed at
> build coverage.
>
> > On the other hand people switching on the option should be able to
> > fix
> > whatever issue
> > arises.
> >
> > And, considering that it was broken since January 2013
> > (dfe64e2c89731a3f9950d7acd8681b68df2bae03) it can not be that
> > important.
>
> This patch fixes a breakage that was merged within the past week.
> What was
> broken by the 2013 sync?
The 2013 sync did deprecate the outside use of the function pointers
in the mtd_info struct. To force this it did also rename the struct
members.
Since the torture code did not follow the rename it did no longer
compile.
Now fixed with
http://git.denx.de/?p=u-boot.git;a=commit;h=667067faa18334f1e28c01b4753
0b5cce1b6182f
Max
>
> -Scott
>
next prev parent reply other threads:[~2016-06-09 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 11:46 [U-Boot] [PATCH v2 1/2] nand: nand torture: follow sync with linux v4.6 Max Krummenacher
2016-06-07 11:46 ` [U-Boot] [PATCH v2 2/2] nand: extend nand torture Max Krummenacher
2016-06-08 23:41 ` Benoît Thébaudeau
2016-06-09 13:19 ` Max Krummenacher
2016-06-09 22:20 ` Benoît Thébaudeau
2016-06-08 23:47 ` [U-Boot] [PATCH v2 1/2] nand: nand torture: follow sync with linux v4.6 Scott Wood
2016-06-09 8:35 ` Max Krummenacher
2016-06-09 17:10 ` Scott Wood
2016-06-09 21:13 ` Max Krummenacher [this message]
2016-06-09 21:16 ` Scott Wood
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=1465506804.3826.5.camel@gmail.com \
--to=max.oss.09@gmail.com \
--cc=u-boot@lists.denx.de \
/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