From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CHANGELOG w/ status update: cmd_of.c, ft_build.c, vsprintf.c, long long print problem
Date: Fri, 13 Oct 2006 09:45:12 -0400 [thread overview]
Message-ID: <452F9868.80609@smiths-aerospace.com> (raw)
In-Reply-To: <20061013133716.31C7B353DA0@atlas.denx.de>
Wolfgang Denk wrote:
> Hello,
>
> in message <452F9380.3010505@smiths-aerospace.com> you wrote:
>> I'm sure other people use it, I read it for entertainment occasionally.
>
> :-) Welcome #2!
>
>> For instance, it is useful to sort the local commit noise from the
>> "official" noise, following what is going on in the main tree.
>
> Indeed. We will lose this filtering when using a git log generated
> file.
>
>>> Is this acceptable to you and everybody else?
>> You bet!
>
> Just for the record: I have a few very busy days in front of me. I
> miught be able to do the first steps on Sunday evening / night, but
> then I'll probably not be able to do anything again before Wednesday.
> So please be patient, if I don't reply immediately this does not mean
> I ignore any messages.
Yes, I understand. Actually, the exclamation marks in my original reply
were for joy that it was happening so soon, I was afraid I would be in
limbo for a lot longer.
>> My git repository:
>> <http://www.cideas.us/git>
>>
>> Project for this discussion:
>> <http://www.cideas.us/cgi-bin/gitweb.cgi?p=u-boot/u-boot-pq2fads.git;a=summary>
>>
>> cmd_of.c, ft_build.c
>
> I understand this might need to be cleaned up after we merged Jon's
> and Matthew's trees, so I will wait until then, OK? Will you please
> trigger me again then?
Yes, that was just for reference in case someone wanted to browse my
changes. I'll submit a proper patch when Jon's stuff is in the main
repo and I can do a clean patch that doesn't conflict with Jon's work
(including clean CHANGELOG type comments ;-).
>> vsprintf.c, long long print problem
> ...
>> I have *NOT* been able to figure out why long long printing is *NOT*
>> working correctly. It does *NOT* work correctly for the "%q" version
>> either. My current theory is that varargs isn't working correctly for
>> long long, but I have not chased down that path (yet).
>
> Did you check the assembler code? Which exact toolchain are you using?
a) No. I'll do that.
b) ELDK4.0 with the 82xx PowerPC target.
> Best regards,
>
> Wolfgang Denk
Thanks,
gvb
next prev parent reply other threads:[~2006-10-13 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 1:14 [U-Boot-Users] Proposed CHANGELOG Generation Helpers Jon Loeliger
2006-10-13 9:52 ` Wolfgang Denk
2006-10-13 13:24 ` [U-Boot-Users] CHANGELOG w/ status update: cmd_of.c, ft_build.c, vsprintf.c, long long print problem Jerry Van Baren
2006-10-13 13:37 ` Wolfgang Denk
2006-10-13 13:45 ` Jerry Van Baren [this message]
2006-10-13 14:37 ` Jon Loeliger
2006-10-13 14:52 ` Jerry Van Baren
2006-10-13 14:28 ` [U-Boot-Users] Proposed CHANGELOG Generation Helpers Jon Loeliger
2006-10-13 14:32 ` Jon Loeliger
2006-10-13 15:33 ` Timur Tabi
2006-10-16 7:14 ` Wolfgang Denk
2006-10-16 14:36 ` Grant Likely
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=452F9868.80609@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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