From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Fri, 13 Oct 2006 09:45:12 -0400 Subject: [U-Boot-Users] CHANGELOG w/ status update: cmd_of.c, ft_build.c, vsprintf.c, long long print problem In-Reply-To: <20061013133716.31C7B353DA0@atlas.denx.de> References: <20061013133716.31C7B353DA0@atlas.denx.de> Message-ID: <452F9868.80609@smiths-aerospace.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.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: >> >> >> Project for this discussion: >> >> >> 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