public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Seperate mtdpart command from jffs2
Date: Mon, 9 Mar 2009 09:14:53 +0100	[thread overview]
Message-ID: <200903090914.53501.sr@denx.de> (raw)
In-Reply-To: <9c9fda240903082008w1e68d1cfpeed2ad836dcd1f49@mail.gmail.com>

On Monday 09 March 2009, Kyungmin Park wrote:
> >> +++ b/common/Makefile
> >> @@ -98,6 +98,7 @@ COBJS-$(CONFIG_CMD_IMMAP) += cmd_immap.o
> >> ?COBJS-$(CONFIG_CMD_IRQ) += cmd_irq.o
> >> ?COBJS-$(CONFIG_CMD_ITEST) += cmd_itest.o
> >> ?COBJS-$(CONFIG_CMD_JFFS2) += cmd_jffs2.o
> >> +COBJS-$(CONFIG_JFFS2_CMDLINE) += cmd_mtdparts.o
> >
> > Shouldn't we change this define (CONFIG_JFFS2_CMDLINE) to something else
> > now, since it's not really JFFS2 specific anymore? I suggest to change it
> > to CONFIG_CMD_MTDPARTS. This seems more logical to me.
> >
> > What do you think?
>
> It's already done by Jean-Christophe PLAGNIOL-VILLARD. Isn't it?

Is it? I have not seen such a patch. Do you have a link? (I added 
Jean-Christophe to CC).

> > This patch also breaks (at least some) boards with JFFS2 support:
> >
> > [stefan at kubuntu u-boot (master)]$ ./MAKEALL fx12mm
> > Configuring for fx12mm board...
> > cmd_jffs2.c:164: warning: 'device_validate' defined but not used
> > cmd_jffs2.c:220: warning: 'id_parse' defined but not used
> > common/libcommon.a(cmd_flash.o): In function `do_protect':
> > /home/stefan/git/u-boot/u-boot/common/cmd_flash.c:568: undefined
> > reference to `id_parse'
> > common/libcommon.a(cmd_flash.o): In function `do_flerase':
> > /home/stefan/git/u-boot/u-boot/common/cmd_flash.c:362: undefined
> > reference to `id_parse'
> > make: *** [u-boot] Error 1
> > ppc_4xx-size: './u-boot': No such file
> >
> >
> > I didn't try to solve this problem (yet). Perhaps you have an idea?
>
> In both case jffs2 and mtdpart, have id_parse as changed to static, so
> one of both should be non-static. I think remove static at cmd_jffs2.c

It would be great if you could fix this issue in your next patch version.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2009-03-09  8:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  5:03 [U-Boot] [PATCH] Seperate mtdpart command from jffs2 Kyungmin Park
2009-03-03  8:41 ` Stefan Roese
2009-03-06 13:13 ` Stefan Roese
2009-03-08 22:12   ` Wolfgang Denk
2009-03-09  3:08   ` Kyungmin Park
2009-03-09  8:14     ` Stefan Roese [this message]
2009-03-09  9:22       ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-09  9:52         ` Stefan Roese
2009-03-09 10:20           ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-09 10:43             ` Stefan Roese
2009-03-09 11:24               ` Wolfgang Denk
2009-03-09 11:23             ` Wolfgang Denk
2009-03-09 20:13         ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-09 21:53           ` Wolfgang Denk

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=200903090914.53501.sr@denx.de \
    --to=sr@denx.de \
    --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