From: Tony Lindgren <tony@atomide.com>
To: twebb <taliaferro62@gmail.com>
Cc: "linux-omap@vger.kernel.org Mailing List" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH OMAPZOOM] OMAP: DMA: Fix CCR programming for request line > 63
Date: Thu, 8 Jan 2009 15:52:33 +0200 [thread overview]
Message-ID: <20090108135233.GL27566@atomide.com> (raw)
In-Reply-To: <dbdb2ea60901080540k740b7a9dscd940bcd0c9f6c01@mail.gmail.com>
* twebb <taliaferro62@gmail.com> [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
next prev parent reply other threads:[~2009-01-08 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 11:08 [PATCH OMAPZOOM] OMAP: DMA: Fix CCR programming for request line > 63 Gadiyar, Anand
2008-11-11 13:33 ` Pandita, Vikram
2009-01-08 13:31 ` Tony Lindgren
2009-01-08 13:40 ` twebb
2009-01-08 13:52 ` Tony Lindgren [this message]
2009-01-08 14:08 ` twebb
2009-01-08 14:20 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090108135233.GL27566@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=taliaferro62@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox