From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fdt: add common memory fixup function
Date: Fri, 26 Oct 2007 07:26:48 -0400 [thread overview]
Message-ID: <4721CEF8.8040709@ge.com> (raw)
In-Reply-To: <77096504-D90D-4732-B0B1-25403C1DE331@kernel.crashing.org>
Kumar Gala wrote:
> On Oct 25, 2007, at 7:01 PM, Wolfgang Denk wrote:
>
>> In message
>> <6A2E9F87-25A3-469E-9541-55D200F10296@kernel.crashing.org> you wrote:
>>> Great, I've got a set of patches for using new libfdt, but I might
>>> put them in a git tree since the libfdt import is big and difficult
>>> to post to the list.
>> You git tree will be likely ignored if you don't post the patches.
>
> I've posted two of the the three patches in my tree.
>
> Any suggestions on how to deal with the third, its beyond the size
> limit for the list?
>
> - k
Hi Kumar,
Individually, the files will fit through the list. Based on sizes, even
if the patches blow up to 2x the current file size, they should still
fit through the list.
$ ls -l
total 88
-rw-r--r-- 1 vanbaren users 4572 2007-10-26 07:18 fdt.c
-rw-r--r-- 1 vanbaren users 1691 2007-10-26 07:18 fdt.h
-rw-r--r-- 1 vanbaren users 12281 2007-10-26 07:18 fdt_ro.c
-rw-r--r-- 1 vanbaren users 9621 2007-10-26 07:18 fdt_rw.c
-rw-r--r-- 1 vanbaren users 3321 2007-10-26 07:18 fdt_strerror.c
-rw-r--r-- 1 vanbaren users 7087 2007-10-26 07:18 fdt_sw.c
-rw-r--r-- 1 vanbaren users 4048 2007-10-26 07:18 fdt_wip.c
-rw-r--r-- 1 vanbaren users 502 2007-10-26 07:18 libfdt_env.h
-rw-r--r-- 1 vanbaren users 17522 2007-10-26 07:18 libfdt.h
-rw-r--r-- 1 vanbaren users 3520 2007-10-26 07:18 libfdt_internal.h
-rw-r--r-- 1 vanbaren users 436 2007-10-26 07:18 Makefile.libfdt
-rw-r--r-- 1 vanbaren users 142 2007-10-26 07:18 TODO
Best regards,
gvb
next prev parent reply other threads:[~2007-10-26 11:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 13:43 [U-Boot-Users] [PATCH] fdt: add common memory fixup function Martin Krause
2007-10-25 14:13 ` Jerry Van Baren
2007-10-25 15:05 ` Kumar Gala
2007-10-26 0:01 ` Wolfgang Denk
2007-10-26 4:57 ` Kumar Gala
2007-10-26 10:00 ` Wolfgang Denk
2007-10-26 11:26 ` Jerry Van Baren [this message]
2007-10-26 14:45 ` Kumar Gala
2007-10-25 14:39 ` Kim Phillips
2007-10-25 15:47 ` Martin Krause
2007-10-25 15:05 ` Kumar Gala
2007-10-25 15:57 ` Martin Krause
2007-10-25 16:08 ` Kim Phillips
-- strict thread matches above, loose matches on Subject: below --
2007-10-26 8:49 Martin Krause
2007-10-26 9:55 ` Kumar Gala
2007-10-26 10:09 ` Martin Krause
2007-10-26 11:14 ` Jerry Van Baren
2007-10-26 11:26 ` Martin Krause
2007-10-26 11:27 ` Jerry Van Baren
2007-10-26 11:47 Martin Krause
2007-11-20 20:34 ` Kumar Gala
2007-11-27 8:02 ` Martin Krause
2007-11-27 14:13 ` Kumar Gala
2007-11-27 16:39 ` Kim Phillips
2007-11-27 17:16 ` Kumar Gala
2007-11-27 17:58 ` Kim Phillips
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=4721CEF8.8040709@ge.com \
--to=gerald.vanbaren@ge.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