All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtdparts: Call nand_init() during mtdparts_init().
Date: Fri, 15 Oct 2010 16:08:29 -0400	[thread overview]
Message-ID: <201010151608.30637.vapier@gentoo.org> (raw)
In-Reply-To: <20101015193640.722281365CF@gemini.denx.de>

On Friday, October 15, 2010 15:36:40 Wolfgang Denk wrote:
> Scott Wood wrote:
> > The mtdparts code depends on the devices referred to by
> > partition specs actually existing, both for error checking,
> > when the spread feature is used, for bad block checking.
> > 
> > @@ -1711,6 +1707,7 @@ int mtdparts_init(void)
> >  		memset(last_ids, 0, MTDIDS_MAXLEN);
> >  		memset(last_parts, 0, MTDPARTS_MAXLEN);
> >  		memset(last_partition, 0, PARTITION_MAXLEN);
> > 
> > +		nand_init();
> >  		initialized = 1;
> >  	}
> 
> I don't like this either.  I don't want to see a nand_init() for
> systems that have no NAND at all (not even an empty one).

i disagree ... sprinkling #ifdef's throughout the code makes it a lot harder 
to read, maintain, and validate across multiple configurations.  you're 
suggesting we do:
#ifdef CONFIG_CMD_NAND
		nand_init();
#endif

it makes more sense to me to hide this in the header (which Scott has done) 
and let the compiler/code optimize dead crap away.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20101015/eaabdd58/attachment.pgp 

  parent reply	other threads:[~2010-10-15 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 18:59 [U-Boot] [PATCH] mtdparts: Call nand_init() during mtdparts_init() Scott Wood
2010-10-15 19:36 ` Wolfgang Denk
2010-10-15 19:47   ` Scott Wood
2010-10-15 20:08   ` Mike Frysinger [this message]
2010-10-15 21:39     ` Wolfgang Denk
2010-10-15 21:48       ` Scott Wood
2010-10-15 22:17         ` Wolfgang Denk
2010-10-15 22:35           ` Scott Wood
2010-10-15 22:48             ` Wolfgang Denk
2010-10-15 23:05               ` 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=201010151608.30637.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.