From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: nand: let the raw NAND devices be compiled upon selection
Date: Mon, 8 Apr 2019 07:54:47 -0400 [thread overview]
Message-ID: <20190408115447.GD4664@bill-the-cat> (raw)
In-Reply-To: <20190408115231.7c9f251d@xps13>
On Mon, Apr 08, 2019 at 11:52:31AM +0200, Miquel Raynal wrote:
> Hi Jagan,
>
> Miquel Raynal <miquel.raynal@bootlin.com> wrote on Mon, 29 Oct 2018
> 10:07:28 +0100:
>
> > Hi Jagan,
> >
> > Jagan Teki <jagan@amarulasolutions.com> wrote on Tue, 23 Oct 2018
> > 16:40:05 +0530:
> >
> > > On Thu, Oct 11, 2018 at 3:05 PM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> > > >
> > > > Today way is to rely on CMD_NAND to be selected and from the root
> > > > Makefile compile what is in drivers/mtd/nand/raw.
> > > >
> > > > While this will work most of the time with decent configurations, it
> > > > is better to also compile this subsystem upon simple request in the
> > > > configuration. Otherwise, a user not selecting CMD_NAND but selecting
> > > > NAND and any of the controller drivers will not see their build. Fix
> > > > this weird situation by adding a single line in the nand/ directory
> > > > Kconfig file.
> > > >
> > > > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> > > > ---
> > > > drivers/mtd/nand/Makefile | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/drivers/mtd/nand/Makefile b/drivers/mtd/nand/Makefile
> > > > index a358bc680e..2c33447995 100644
> > > > --- a/drivers/mtd/nand/Makefile
> > > > +++ b/drivers/mtd/nand/Makefile
> > > > @@ -2,4 +2,5 @@
> > > >
> > > > nandcore-objs := core.o bbt.o
> > > > obj-$(CONFIG_MTD_NAND_CORE) += nandcore.o
> > > > +obj-$(CONFIG_NAND) += raw/
> > >
> > > But we even source raw Kconfig path, isn't it? and also how about
> > > remove this from root Makefile?
> >
> > What do you mean by "we even source raw Kconfig path"? It was not
> > sourced before this modification unless CMD_NAND was selected.
> >
> > I agree we should also remove this link between a path being
> > compiled and a CMD_* symbol in the root Makefile. It will probably
> > produce a lot of errors though. I'll try when I'll have some time.
>
> Yet another patch you ignored. All these are real fixes, not just some
> kind of sandbox leisure, please consider this change.
Yes, what's going on here? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190408/87dc41d7/attachment.sig>
next prev parent reply other threads:[~2019-04-08 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 9:35 [U-Boot] [PATCH] mtd: nand: let the raw NAND devices be compiled upon selection Miquel Raynal
2018-10-23 11:10 ` Jagan Teki
2018-10-29 9:07 ` Miquel Raynal
2018-11-05 5:02 ` Jagan Teki
2019-04-08 9:52 ` Miquel Raynal
2019-04-08 11:54 ` Tom Rini [this message]
2019-04-08 11:58 ` Jagan Teki
2019-04-08 13:20 ` Miquel Raynal
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=20190408115447.GD4664@bill-the-cat \
--to=trini@konsulko.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