From: Arnd Bergmann <arnd@arndb.de>
To: artem.bityutskiy@linux.intel.com
Cc: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"tony@atomide.com" <tony@atomide.com>,
"jp.francois@cynove.com" <jp.francois@cynove.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"avinashphilipk@gmail.com" <avinashphilipk@gmail.com>,
"Balbi, Felipe" <balbi@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Gupta, Pekon" <pekon@ti.com>, "olof@lixom.net" <olof@lixom.net>,
"benoit.cousson@linaro.org" <benoit.cousson@linaro.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v4 0/4] mtd:nand:omap2: clean-up of supported ECC schemes
Date: Wed, 3 Jul 2013 15:27:16 +0200 [thread overview]
Message-ID: <201307031527.17219.arnd@arndb.de> (raw)
In-Reply-To: <1372857987.9767.162.camel@sauron.fi.intel.com>
On Wednesday 03 July 2013, Artem Bityutskiy wrote:
> On Wed, 2013-07-03 at 13:16 +0000, Gupta, Pekon wrote:
> > [Pekon]: Yes, I'm not seeing these build issues, as I'm cleanly
> > returning from probe with pr_err(), if the required libraries (/lib/bch.c)
> > are not build-in the system.
> > -------------------
> > [Patch v4 1/4]: mtd:nand:omap2: clean-up BCHx_HW and BCHx_SW ECC..
> > @@static int omap_nand_probe(struct platform_device *pdev)
> > + default:
> > + pr_err("selected ECC scheme not supported or not enabled\n");
> > + err = -EINVAL;
> > + goto out_release_mem_region;
> > + }
> > -------------------
> > However, if you are still seeing this, could you please send me your config?
>
> I compile tested your patches too, and did not see any issues with my
> omap2_defconfig.
To clarify: I'm getting this error with randconfig on today's linux-next.
I think it only happens with MTD_NAND_ECC_BCH enabled, which is not
the default in omap2_defconfig.
Arnd
next prev parent reply other threads:[~2013-07-03 13:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 11:32 [PATCH v4 0/4] mtd:nand:omap2: clean-up of supported ECC schemes Pekon Gupta
2013-07-02 11:32 ` [PATCH v4 1/4] mtd:nand:omap2: clean-up BCHx_HW and BCHx_SW ECC configurations in device_probe Pekon Gupta
2013-07-02 11:32 ` [PATCH v4 2/4] ARM: OMAP2+: cleaned-up DT support of various ECC schemes Pekon Gupta
2013-07-08 4:37 ` Gupta, Pekon
2013-07-02 11:32 ` [PATCH v4 3/4] mtd:nand:omap2: updated support for BCH4 ECC scheme Pekon Gupta
2013-07-02 11:32 ` [PATCH v4 4/4] ARM: dts: AM33xx: updated default ECC scheme in nand-ecc-opt Pekon Gupta
2013-07-03 13:03 ` [PATCH v4 0/4] mtd:nand:omap2: clean-up of supported ECC schemes Arnd Bergmann
2013-07-03 13:16 ` Gupta, Pekon
2013-07-03 13:26 ` Artem Bityutskiy
2013-07-03 13:27 ` Arnd Bergmann [this message]
2013-07-03 18:04 ` Gupta, Pekon
2013-07-04 16:57 ` Mugunthan V N
2013-07-05 4:12 ` Gupta, Pekon
-- strict thread matches above, loose matches on Subject: below --
2013-07-01 9:51 Pekon Gupta
2013-07-01 10:43 ` Artem Bityutskiy
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=201307031527.17219.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=avinashphilipk@gmail.com \
--cc=balbi@ti.com \
--cc=benoit.cousson@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jp.francois@cynove.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pekon@ti.com \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
/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