From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Separate 83xx, 85xx, and 86xx configurations into their own Makefiles
Date: Fri, 26 Jan 2007 09:47:10 -0600 [thread overview]
Message-ID: <45BA227E.2020509@freescale.com> (raw)
In-Reply-To: <20070126154333.73FEC353CC1@atlas.denx.de>
Wolfgang Denk wrote:
> In message <11698248351613-git-send-email-timur@freescale.com> you wrote:
>> This patch moves the board configuration rules for 83xx, 85xx, and 86xx boards
>> into their own makefiles. All 83xx boards are now configured in Makefile.83xx,
>> all 85xx boards are in Makefile.85xx, and all 86xx boards are in Makefile.86xx.
>> With separate maintainers for these families, this patch allows new boards
>> to be added without having merge conflicts.
>
> I reject this patch. The Makefile may be long, but I rather have all
> information in one place.
Are you interested in any changes that divide the families into their own
directories?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-01-26 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 15:20 [U-Boot-Users] [PATCH] Separate 83xx, 85xx, and 86xx configurations into their own Makefiles Timur Tabi
2007-01-26 15:43 ` Wolfgang Denk
2007-01-26 15:47 ` Timur Tabi [this message]
2007-01-26 16:07 ` 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=45BA227E.2020509@freescale.com \
--to=timur@freescale.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.