* twebb [090108 16:08]:
> >
> > 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
>
> 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, whi
* twebb [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
>
> 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 unde
-omap@vger.kernel.org
> >Cc: Pandita, Vikram; t...@atomide.com
> >Subject: [PATCH OMAPZOOM] OMAP: DMA: Fix CCR programming for request line >
> >63
> >
> >From: Anand Gadiyar
> >
> >Bug in existing code causes synchro control to be set +32 if request
> >l
Pushed to zoom tree.
>-Original Message-
>From: Gadiyar, Anand
>Sent: Monday, November 10, 2008 5:08 AM
>To: linux-omap@vger.kernel.org
>Cc: Pandita, Vikram; [EMAIL PROTECTED]
>Subject: [PATCH OMAPZOOM] OMAP: DMA: Fix CCR programming for request line > 63
>
>
From: Anand Gadiyar <[EMAIL PROTECTED]>
Bug in existing code causes synchro control to be set +32 if request
line greater than 63 is used.
Reported by Wenbiao Wang
Signed-off-by: Anand Gadiyar <[EMAIL PROTECTED]>
---
Patch generated against OMAPZOOM tree. Will apply against
linux-omap as well wi
