From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CONFIG_CMD_* transition and other config changes
Date: Fri, 6 Jul 2007 09:54:45 +0200 [thread overview]
Message-ID: <200707060954.45223.matthias.fuchs@esd-electronics.com> (raw)
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
--
-----------------------------------------------------------------------
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
-----------------------------------------------------------------------
next reply other threads:[~2007-07-06 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 7:54 Matthias Fuchs [this message]
2007-07-06 9:06 ` [U-Boot-Users] CONFIG_CMD_* transition and other config changes 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=200707060954.45223.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.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 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.