From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] mtd: nand: Support for new DT NAND driver
Date: Wed, 20 Aug 2014 07:57:44 +0100 [thread overview]
Message-ID: <20140820065744.GE4266@lee--X1> (raw)
In-Reply-To: <20140819013729.GP18411@ld-irv-0074>
On Mon, 18 Aug 2014, Brian Norris wrote:
> On Mon, Aug 18, 2014 at 11:31:51AM +0100, Lee Jones wrote:
> > I believe all of your queries have either been answered or addressed
> > and I am hoping this will be the last submission. :)
>
> Sorry, no. I can't review code that doesn't compile, so I'm only now
> getting to some of the review.
>
> > This is v2 of the squashed submission. v1 had a small typo which
> > prevented the BBT code from being truly configurable. This has now
> > been rectified and build tested with and without MTD_NAND_STM_BCH_BBT
> > support.
>
> From smatch:
>
> drivers/mtd/nand/stm_nand_bch.c:1556 stm_nand_bch_probe() error:
> we previously assumed 'bank' could be null (see line 1482)
> [smatch]
I have now built and installed smatch - it is now part of my built
scripts.
> From GCC (extra warnings):
>
> drivers/mtd/nand/stm_nand_dt.c:39:21: warning: no previous
> prototype for 'stm_of_get_partitions_node' [-Wmissing-prototypes]
> drivers/mtd/nand/stm_nand_dt.c:68:5: warning: no previous
> prototype for 'stm_of_get_nand_banks' [-Wmissing-prototypes]
My build scripts now support extended warnings to level 1. This was a
pain to get working, as my scripts also build DTBS, which has a side
effect of re-compiling everything, every time. This was fixed by also
issuing W=1 on the `make $(make_options) $(extra_build_options) dtbs`
line.
> Looks like you forgot to include <linux/mtd/stm_nand_bbt.h>.
This had me confused for a little while. I think you mean:
#include "stm_nand_dt.h".
Basically, the DT code wasn't including its own header file.
Caught and fixed.
> And your code is not bisectable. I think patch 7 and 8 should be
> reordered (with some tweaks, perhaps):
Now fixed.
I have split out the BBT header file and applied it first.
> Bisectability test results for configuration
> "arm-multi_v7_defconfig,arm,arm-unknown-linux-gnueabi-"
>
> Failed to build patch #7: 5936df30f5e1 mtd: nand: stm_nand_bch: add
> support for ST's BCH NAND controller
> Configuration: "arm-multi_v7_defconfig, architecture arm".
How do _you_ test for bisectability? Do you have a script?
What outputs "Failed to build patch #7: ..."?
[...]
> drivers/mtd/nand/stm_nand_bch.c:26:36: fatal error:
> linux/mtd/stm_nand_bbt.h: No such file or directory
> compilation terminated.
> make[4]: *** [drivers/mtd/nand/stm_nand_bch.o] Error 1
Fixed.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-08-20 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 10:31 [PATCH v2 0/8] mtd: nand: Support for new DT NAND driver Lee Jones
2014-08-18 10:31 ` [PATCH 1/8] ARM: multi-v7: Enable ST BCH NAND Lee Jones
2014-08-18 10:31 ` [PATCH 2/8] ARM: sti: Add two new clock definitions for use with ST's NAND controllers Lee Jones
2014-08-18 10:31 ` [PATCH 3/8] ARM: sti: Add BCH (NAND Flash) Controller support for STiH41x (Orly) SoCs Lee Jones
2014-08-18 10:31 ` [PATCH 4/8] ARM: sti: Enable BCH NAND for STiH416 B2020-RevE Lee Jones
2014-08-18 10:31 ` [PATCH 5/8] mtd: nand: stm_nand_bch: provide Device Tree documentation Lee Jones
2014-08-18 10:31 ` [PATCH 6/8] mtd: nand: add shared register defines for ST's NAND Controller drivers Lee Jones
2014-08-18 10:31 ` [PATCH 7/8] mtd: nand: stm_nand_bch: add support for ST's BCH NAND controller Lee Jones
2014-08-19 1:52 ` Brian Norris
2014-08-18 10:31 ` [PATCH 8/8] mtd: nand: stm_nand_bch: provide ST's implementation of Back Block Table Lee Jones
2014-08-19 1:37 ` [PATCH v2 0/8] mtd: nand: Support for new DT NAND driver Brian Norris
2014-08-20 6:57 ` Lee Jones [this message]
2014-10-02 6:18 ` Brian Norris
2014-10-08 10:41 ` Lee Jones
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=20140820065744.GE4266@lee--X1 \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@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