in
this case).
Signed-off-by: Olof Johansson olof@lixom.net
Ack-ed
Sandeep, Can you push this to the ti branch?
Tom
Yes after I rebase the branch. I have to get rid of some commits NAK'ed by Wolfgang.
Seems this is done :)
Just in case it might help: After looking through the OMAP3 patches, my list of patches to be applied:
- [PATCH v3] OMAP3 MMC: Fix warning dereferencing type-punned pointer
http://lists.denx.de/pipermail/u-boot/2009-September/061621.html
- [PATCH] OMAP3: Update Overo and Beagle environment
http://lists.denx.de/pipermail/u-boot/2009-September/061564.html
- [PATCH 1/1] TI OMAP3 Use arm init sequence to initialize i2c
http://lists.denx.de/pipermail/u-boot/2009-September/061515.html
(if it's fine to move it into u-boot-ti instead of u-boot-i2c)
Looks like you have an ACK for this to happen :-)
- [PATCH] OMAP3: Clean up whitespace in mux configs
http://lists.denx.de/pipermail/u-boot/2009-September/061300.html
- [PATCH v3] TI: OMAP3: Overo Tobi ethernet support
http://lists.denx.de/pipermail/u-boot/2009-September/061604.html
(needs an ack from Ben?)
Note: 5 depends on 4.
Best regards
Dirk
I'll apply them in the evening.
Thanks for applying patches 1, 2 & 4 :)
#3 does not apply clean :-) #5 I'm waiting for a reply from Ben
Just fyi, I got
u-boot-ti > git pull remote: error: refs/remotes/origin/HEAD points nowhere! remote: error: refs/remotes/origin/mkimage does not point to a valid object! ...
I am able to pull without any issues. Things seem fine. You should be able to see all you updates in the repo you just updated
Not sure what this is about, though.
Is there anything I can do to get rid of this?
Best regards
Dirk