Re: upstream merge schedule

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Daniel Walker <dwalker@xxxxxxxxxx> [080117 21:57]:
> 
> When I made the nokia770 patch (just sent) I was wonder when it would be
> merged? It seems that omap upstream merges are somewhat slow going, why
> is that?

Ideally patches should get merged to linux-omap within few days
and in more intrusive cases within few weeks. But sometimes patches
pile up, and now we have some patches pending mostly because I
was travelling for three weeks. I will be applying patches starting
today, so hopefully we'll have the pending patches cleared up within
next few days.

Regarding merging core omap stuff to mainline kernel, we still need
to clean up few things to get arch/arm/*omap directories in sync with
mainline. After currently pending patches arch/arm/mach-omap1 and
plat-omap will be within one or two more main releases away from
being in sync, and mach-omap2 will take a bit longer. So hopefully
we'll be in sync with mainline for core omap stuff during this year.

Regarding merging various drivers upstream, they need to go through
various driver mailing lists or LKML. So ideally the person who has
done the patch will also send it for merging to the right mailing
list. Otherwise the driver patch will most likely just stay in
linux-omap tree.

Regards,

Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux