public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: Kyungmin Park <kmpark@infradead.org>,
	linux-omap-open-source@linux.omap.com
Subject: Re: About to tag 2.6.23-omap1
Date: Mon, 29 Oct 2007 01:49:28 -0700	[thread overview]
Message-ID: <20071029084928.GG10884@atomide.com> (raw)
In-Reply-To: <20071023174000.GH5193@atomide.com>

* Tony Lindgren <tony@atomide.com> [071023 10:41]:
> * Dirk Behme <dirk.behme@googlemail.com> [071023 08:30]:
> > Kyungmin Park wrote:
> >> There is a pending patch related with OMAP2 USB device DMA support.
> >> I think now there's one user to use this feature, Apollon.
> >> As David's comment, it has board specific code.
> >> but the DMA patch don't update the board specific code. it only adds
> >> the DMA codes.
> >> So if you don't mind I hope to merge this one too.
> >
> > Looking into my pending patches list, I think you mean
> >
> > http://linux.omap.com/pipermail/linux-omap-open-source/2007-October/011579.html
> >
> > ?
> 
> Let's plan on pushing that over after updating to current mainline
> kernel. That way if it breaks stuff for non-DMA configurations :)
> 
> >> On 10/23/07, Tony Lindgren <tony@atomide.com> wrote:
> >>> Hi all,
> >>>
> >>> I'm planning to tag 2.6.23-omap1 tomorrow morning PST with current
> >>> linux-omap git tree unless somebody comes up with fixes that still
> >>> should go in.
> >>>
> >>> So only fixes right now please, then let's update the tree to
> >>> mainline kernel, and try to get most of the pending patches such as
> >>> mmc, v4l, osk-2420, omap2-nand etc applied (and fixed if needed).
> >>>
> >>> After that, let's plan on doing the move of arch/arm/plat-omap/dsp
> >>> to drivers/dsp/omap. And then we prepare patches do the fixes needed
> >>> for Russell for plat-omap and mach-omap1 before 2.6.24-rc5 to try to
> >>> get them mostly in sync with mainline. Then we can hopefully sync up
> >>> mach-omap2 for 2.6.25-rc5.
> 
> I've tagged v2.6.23-omap1 and posted the patch to usual location.

Just FYI everybody, I'm updating linux-omap to mainline tree today.

I had to travel to go deal with some product specific bugs, but now that's
out of the way so I'll have more time for linux-omap tree again.

Cheers,

Tony

      parent reply	other threads:[~2007-10-29  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23  1:19 About to tag 2.6.23-omap1 Tony Lindgren
2007-10-23  1:45 ` Kyungmin Park
2007-10-23 15:29   ` Dirk Behme
2007-10-23 17:40     ` Tony Lindgren
2007-10-23 19:16       ` SPI support working? Heilpern, Mark
2007-10-23 19:43         ` Woodruff, Richard
2007-10-23 19:53           ` Heilpern, Mark
2007-10-23 23:11       ` About to tag 2.6.23-omap1 Kyungmin Park
2007-10-29  8:49       ` Tony Lindgren [this message]

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=20071029084928.GG10884@atomide.com \
    --to=tony@atomide.com \
    --cc=dirk.behme@googlemail.com \
    --cc=kmpark@infradead.org \
    --cc=linux-omap-open-source@linux.omap.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