From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: what is the purpose of config option HAS_OMAP_NAND?
Date: Tue, 7 Feb 2012 06:00:02 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1202070559330.17306@oneiric> (raw)
In-Reply-To: <20120207105141.GC3852@pengutronix.de>
On Tue, 7 Feb 2012, Sascha Hauer wrote:
> On Mon, Feb 06, 2012 at 04:14:45PM -0500, Robert P. J. Day wrote:
> >
> > based on the output from grep:
> >
> > $ grep -r HAS_OMAP_NAND *
> > arch/arm/mach-omap/Kconfig: select HAS_OMAP_NAND
> > arch/arm/mach-omap/Kconfig: select HAS_OMAP_NAND
> > arch/arm/mach-omap/Kconfig: select HAS_OMAP_NAND
> > arch/arm/mach-omap/Kconfig: select HAS_OMAP_NAND
> > arch/arm/mach-omap/Kconfig:config HAS_OMAP_NAND
> > arch/arm/configs/phycard_a_l1_defconfig:CONFIG_HAS_OMAP_NAND=y
> > $
> >
> > i'm not sure of the purpose of that Kconfig option. if nothing in the
> > source tree tests it, what value does it have? the definition of that
> > option is simply:
> >
> > config HAS_OMAP_NAND
> > bool
> >
> > am i missing something subtle?
>
> I can only guess that the nand driver depended on this. We can remove
> this.
do you want me to submit a patch? or are you already handling it?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-02-07 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 21:14 Robert P. J. Day
2012-02-07 10:51 ` Sascha Hauer
2012-02-07 11:00 ` Robert P. J. Day [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=alpine.DEB.2.02.1202070559330.17306@oneiric \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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