All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Brian Austin <brian.austin@cirrus.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: is omap development at git tree on kernel.org
Date: Fri, 10 Feb 2012 10:26:14 -0800	[thread overview]
Message-ID: <20120210182614.GR1426@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1202070849400.24880@heelrod.ad.cirrus.com>

* Brian Austin <brian.austin@cirrus.com> [120207 06:23]:
> On Mon, 6 Feb 2012, Tony Lindgren wrote:
> 
> >Yes that's the current URL. For most part all the code is in the
> >mainline kernel, and the linux-omap git tree is used for staging
> >the patches for every merge window. Right now the focus is getting
> >all the fixes into the -rc cycle, and over next few weeks we'll
> >get busy merging all the new code posted for the next merge window.
> >
> >For stable versions, the latest stable mainline version is the
> >way to go, so that's v3.2.x right now. For development versions,
> >mainline v3.3-rc3 will contain the fixes you mentioned above.
> >
> 
> Thanks for the info Tony,
> 
> Just to give you some background,  I do my codec development on a
> "beagleboard like" system and use the for-next branch of ASoC for
> codec patches.  I have noticed some issues with the latest OMAP port
> in this branch and have seem the emails lately from Russell...
> 
> I have seen these issues for a while and would be more than happy to
> inform the OMAP folks of problems with the latest dev branches, kind
> of like a regression tester for you.  If I find something and can
> fix with a patch to email this list, what linux-omap branch should I
> base the patch off of?

Usually for fixes, it's best to base them on most recent mainline
tag that works. So right now either v3.2 or v3.3-rc3.

Regards,

Tony

      reply	other threads:[~2012-02-10 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 23:05 is omap development at git tree on kernel.org Brian Austin
2012-02-06 23:16 ` Tony Lindgren
2012-02-07 14:53   ` Brian Austin
2012-02-10 18:26     ` 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=20120210182614.GR1426@atomide.com \
    --to=tony@atomide.com \
    --cc=brian.austin@cirrus.com \
    --cc=linux-omap@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.