From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Changes to U-Boot Development Process
Date: Thu, 18 Jan 2007 15:20:27 -0600 [thread overview]
Message-ID: <45AFE49B.8080909@freescale.com> (raw)
In-Reply-To: <20070118211045.9C654353CCB@atlas.denx.de>
Wolfgang Denk wrote:
> Nevertheless, I see actually no reason to change the size limit. I
> haven't seen any many board/ directories that exceed 40..50 kB in
> size, and if you compress the patch than the size limit should not
> affect you.
Well, compressing makes it difficult to read inside an email. I think patches
shouldn't be compressed.
However, I don't know why you would say that adding a new board should be under
40KB. Adding a new board typically requires two files: a header file in
include/configs/, and a .c file in board/xxx/. The .c file is actually
accompanied by a config file, a Makefile, an lds file, and maybe some other .c
files.
The sum total of all these files is usually more than 40KB. I think what you're
suggesting is that the patch be divided into two patches: one that contains the
header file, and the other that contains the rest, but that doesn't make sense.
All of these files belong together as a single commit, because U-Boot can't be
compiled without all of them together.
I think the 40KB limit should be increased to 100KB. That's enough to support
all files for an entire board.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-01-18 21:20 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 21:24 [U-Boot-Users] Changes to U-Boot Development Process Wolfgang Denk
2007-01-18 0:36 ` Scott McNutt
2007-01-18 11:18 ` Rodolfo Giometti
2007-01-18 14:46 ` Jerry Van Baren
2007-01-18 14:51 ` Josh Boyer
2007-01-18 16:25 ` Wolfgang Denk
2007-01-18 16:23 ` Wolfgang Denk
2007-01-18 17:40 ` Kim Phillips
2007-01-18 21:10 ` Wolfgang Denk
2007-01-18 21:20 ` Timur Tabi [this message]
2007-01-18 21:40 ` Wolfgang Denk
2007-01-19 7:17 ` Stefan Roese
2007-01-19 7:37 ` Grant Likely
2007-01-19 10:08 ` Wolfgang Denk
2007-01-19 14:35 ` Grant Likely
2007-01-19 14:58 ` Timur Tabi
2007-01-19 10:05 ` Wolfgang Denk
2007-01-19 10:19 ` Stefan Roese
2007-01-19 15:05 ` Timur Tabi
2007-01-19 12:03 ` Josh Boyer
2007-01-19 16:18 ` Haavard Skinnemoen
2007-01-18 18:50 ` Rodolfo Giometti
2007-01-18 21:12 ` Wolfgang Denk
2007-01-19 10:23 ` Tolunay Orkun
2007-01-19 16:03 ` Haavard Skinnemoen
2007-01-19 16:21 ` Jerry Van Baren
2007-01-20 21:33 ` Michal Simek
2007-01-21 20:24 ` Guennadi Liakhovetski
2007-01-21 20:39 ` Wolfgang Denk
2007-01-21 20:49 ` Guennadi Liakhovetski
2007-01-22 9:23 ` Sam Song
2007-01-22 22:04 ` Wolfgang Denk
2007-01-26 4:22 ` Aubrey Li
2007-01-26 9:54 ` Wolfgang Denk
2007-01-26 8:31 ` Aubrey Li
2007-01-26 9:54 ` Wolfgang Denk
2007-01-26 13:38 ` Jerry Van Baren
2007-01-26 15:52 ` Aubrey Li
2007-01-26 16:06 ` Wolfgang Denk
2007-01-26 8:49 ` Grant Likely
2007-01-26 11:46 ` Josh Boyer
2007-01-26 14:36 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2007-02-01 11:31 Peter.Pearse
2007-02-01 15:37 ` Grant Likely
2007-02-08 0:52 Wolfgang Denk
2007-02-08 15:12 ` Rodolfo Giometti
2007-02-12 9:47 Peter Pearse
2007-03-05 23:09 Wolfgang Denk
2007-03-06 6:46 ` Aubrey Li
2007-03-06 9:19 ` Wolfgang Denk
2007-03-06 9:29 ` Aubrey Li
2007-03-06 10:47 ` Wolfgang Denk
2007-03-06 10:52 ` Aubrey Li
2007-03-06 7:57 ` Rodolfo Giometti
2007-03-06 10:08 ` Wolfgang Denk
2007-03-06 10:28 ` Rodolfo Giometti
2007-03-06 15:42 ` Jon Loeliger
2007-03-06 15:59 ` Wolfgang Denk
2007-03-06 16:05 ` Jon Loeliger
2007-03-06 16:11 ` Jerry Van Baren
2007-03-06 16:29 ` Wolfgang Denk
2007-03-06 16:27 ` Wolfgang Denk
[not found] <20070306103035.GE6726@gundam.enneenne.com>
2007-03-06 12:47 ` Wolfgang Denk
[not found] <006d01c75fca$03b87040$0f4565d5@atmel.com>
2007-03-06 14:12 ` Peter Pearse
2007-03-06 14:49 ` 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=45AFE49B.8080909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox