Re: [PATCH OMAPZOOM] OMAP: DMA: Fix CCR programming for request line > 63

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

 



* twebb <taliaferro62@xxxxxxxxx> [090108 15:40]:
> >
> > Sorry for the long delay with this. Pushing to l-o tree and
> > added to omap-fixes queue.
> >
> 
> Probably understood by most of you, but what is the difference between
> "pushing to l-o tree" and "adding to omap-fixes queue"?  What are the
> omap-fixes queued for if not the l-o tree?  I'm trying to understand
> the flow of fixes/changes in the l-o tree, but it's obviously not
> clear to me yet.

Well l-o tree is short for the linux-omap tree. Then I have various
queues of stuff going into the mainline kernel:

omap-fixes
omap-upstream
omap1-upstream
omap2-upstream
omap3-upstream
...

Out of these queues omap-fixes will be sent out as needed during the
-rc cycle, while omap*-upstream queues are stuff for the next merge
window.

These branches show up at the git web interface at the bottom:

http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary

Not that many patches in these queues right now, btw.

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