CONFIG_CMD_* transition and other config changes
Hi,
how should I handle this situation:
1) I plan to update our board configs to the new CONFIG_CMD_* style.
2) I have a couple of patches that update our boards to use the new NAND subsystem instead of the legacy NAND stuff.
Do I have to post the CONFIG_CMD series of patches against u-boot-testing and the NAND patches against the main repository? Or should I post the NAND related patches aginast main repository first and COFNIG_CMD patches that also contain the NAND stuff? So both patches for each board have the NAND stuff in common?
Thanks for advice
Matthias
Signature · 5 lines
----------------------------------------------------------------------- Dipl.-Ing. Matthias Fuchs esd electronic system design gmbh http://www.esd-electronics.com Vahrenwalder Str. 207 phone: +49-511-37298-0, fax: -68 30165 Hannover, Germany -----------------------------------------------------------------------
Quoted 6 lines · In message <[email protected]> you wrote:
how should I handle this situation:
1) I plan to update our board configs to the new CONFIG_CMD_* style.
2) I have a couple of patches that update our boards to use the new NAND subsystem instead of the legacy NAND stuff.
Sounds like being two independent steps to bme, so please create orthogonal patches, too.
Quoted 2 lines
Do I have to post the
CONFIG_CMDseries of patches against u-boot-testing and the NAND patches against the main repository? Or should I post the
Yes, that sounds logical to me.
Quoted 3 lines
NAND related patches aginast main repository first and
COFNIG_CMDpatches that also contain the NAND stuff? So both patches for each board have the NAND stuff in common?
These things are independet of each other.
Best regards,
Wolfgang Denk
Signature · 5 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
No journaling file system can recover your data if the disk dies.
- Steve Rago in <[email protected]>