From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Date: Tue, 23 Feb 2010 14:05:08 -0600 Subject: [U-Boot] Please pull u-boot-ti/master In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D9BC47911@dlee01.ent.ti.com> References: <1266461143-8530-1-git-send-email-s-paulraj@ti.com> <0554BEF07D437848AF01B9C9B5F0BC5D9BB7DE7E@dlee01.ent.ti.com> <4B83FA64.7050002@windriver.com> <0554BEF07D437848AF01B9C9B5F0BC5D9BC47911@dlee01.ent.ti.com> Message-ID: <4B8434F4.7060505@windriver.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Paulraj, Sandeep wrote: > >> -----Original Message----- >> From: Tom [mailto:Tom.Rix at windriver.com] >> Sent: Tuesday, February 23, 2010 10:55 AM >> To: Paulraj, Sandeep >> Cc: u-boot at lists.denx.de; Ben Warren >> Subject: Re: [U-Boot] Please pull u-boot-ti/master >> >> Paulraj, Sandeep wrote: >>> Tom, >>> >>>> The following changes since commit >>>> 77e7273c40315abd2f3c17ad8d46a78950e3e65f: >>>> Jens Scharsig (1): >>>> new board (eb_cpux9k2) >>>> >>>> are available in the git repository at: >>>> >>>> git://git.denx.de/u-boot-ti.git master >>>> >>>> Ladislav Michl (8): >>>> NetStar: eeprom - undefined reference to `memset' >>>> NetStar: eeprom - be less verbose >>>> NetStar: eeprom - fix linker error >>>> NetStar: fix default environment >>>> NetStar: make mtdparts default ready for recent kernels >>> You have already pulled in the 5 patches above. I thought I'd let you >> know. >> >> Yes. I have these. >> >>>> netstar.h: do not exceed 80 columns >>>> VoiceBlue: limit line lenght to 80 characters >>>> VoiceBlue: fix linker errors >> I did not see a public ack for this one. > > http://lists.denx.de/pipermail/u-boot/2010-February/067840.html > > I did so for the other as well I believe. I believe i did not see the linker one. Just checking.. Ok >>>> Nick Thompson (1): >>>> da830evm: Add support for TI EMAC >> Should this go through NET ? > > This does not add the driver. That patch was ACK'ed by Ben long ago. > This patch just does the PINMUX init and invokes the driver. > Ok >> Tom > > Sandeep