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: Mon, 6 Feb 2012 15:16:37 -0800 [thread overview]
Message-ID: <20120206231637.GC20333@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1202061702130.13460@heelrod.ad.cirrus.com>
Hi Brian,
* Brian Austin <brian.austin@cirrus.com> [120206 14:40]:
> Looking at the GIT logs for the linux-omap.git tree it seems pretty
> sparse like no for-next activity in quite a while.
>
> I am using the OMAP for development and need to keep current with
> your platform.
>
> So the questionis...
>
> Is git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
> where the development is being done? I know that the kernel.org
> servers were down for a while and maybe the omap tree hasnt been
> fully updated from another remote one somewhere else? Or is the
> fixes branch where all the work is done?
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.
Regards,
Tony
next prev parent reply other threads:[~2012-02-06 23:16 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 [this message]
2012-02-07 14:53 ` Brian Austin
2012-02-10 18:26 ` 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=20120206231637.GC20333@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).