On 22/12/13 13:53, Hans de Goede wrote:
Hi,
On 12/22/2013 10:49 AM, Alejandro Mery wrote:
On 18/12/13 09:14, Hans de Goede wrote:
Hi,
On 12/18/2013 06:06 AM, Olliver Schinagl wrote:
On 18-12-13 00:07, Hans de Goede wrote:
Hi All,
I've been working on getting together all the great work people are
doing for the upstream kernel into one tree. The result is available
here:
https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-next
This consists of:
base: 3.13-rc4 +
Emilio's clk branch
David's and my mmc work
Chen's gmac work
Oliver's ahci work
sunxi-bits of:
https://git.linaro.org/people/daniel.lezcano/linux.git/shortlog
https://github.com/mripard/linux/commits/sunxi/core-for-3.14
https://github.com/mripard/linux/commits/sunxi/dt-for-3.14
Carlo Caione's rtc work
Arokux' ehci work
Compared to my last tree this adds usb (ehci only for now) support,
rtc
support, high speed timers and some other bits.
Isn't this the same as sunxi-next (but more up to date?)
Ah you mean:
https://github.com/linux-sunxi/linux-sunxi/commits/sunxi-next
That just has the bits which will be going upstream through mripard,
and as such is missing a lot of stuff my tree has (which will go
upstream through other tress and/or is not completely ready yet).
sunxi-devel was supposed to collect the things for upstream but not
accepted (or acceptable) yet.... can these efforts be joined?
Yes please. If you can give me push access to the linux-sunxi github
repo I'll gladly rename my branch to sunxi-devel and push my work
there. As it seems that I'm most active on this front atm, I guess it
is best for me to maintain this branch.
granted. please coordinate things with Turl as well.
I'm currently rebasing on top of Linus' rc releases, and then doing
a forced push, I greatly prefer this over doing merges, as it makes
it clear to see what is in the branch on top of upstream.
I think sunxi-devel is already a rebased branch
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
