From: "G, Manjunath Kondaiah" <manjugk@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Code for v2.6.39 merge window frozen, patches archived
Date: Wed, 16 Mar 2011 19:37:10 +0530 [thread overview]
Message-ID: <20110316140710.GA10385@m-desktop> (raw)
In-Reply-To: <20110314192538.GH7258@atomide.com>
On Mon, Mar 14, 2011 at 12:25:38PM -0700, Tony Lindgren wrote:
> Hi all,
>
> I've applied few random fix like patches today into omap-for-linus
> but that's it for this merge window.
>
> So let's do some testing with with Stephen's for-next and
> omap-for-linus and start queueing up fixes for the -rc cycle.
omap-for-linus boots on:
OMAP3430-Zoom2
OMAP3630-Zoom3
OMAP4430-Blaze
With OMAP3 and OMAP4 disabled, it boots successfully on:
OMAP2420-H4
OMAP2430-SDP
-Manjunath
>
> I've also moved all the patchwork.kernel.org patches into
> archived-v2.6.39 bundle and marked them as archived:
>
> https://patchwork.kernel.org/user/bundle/1381/
>
> You can still find the patches there if you click on Filters
> and changed Archived from No to Both.
>
> Looks like there's one smartreflex patch that does not seem
> to exist in patchwork though.. So that one is still lurking
> around on the patchwork list of patches until the issue has
> been fixed in patchwork.kernel.org.
>
> Cheers,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-16 14:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 19:25 Code for v2.6.39 merge window frozen, patches archived Tony Lindgren
2011-03-15 3:05 ` Nishanth Menon
2011-03-15 15:09 ` Kevin Hilman
2011-03-15 15:20 ` Menon, Nishanth
2011-03-15 17:54 ` Aaro Koskinen
2011-03-15 20:07 ` Cousson, Benoit
2011-03-15 20:32 ` aaro.koskinen
2011-03-16 13:49 ` Aaro Koskinen
2011-03-16 14:33 ` Cousson, Benoit
2011-03-16 15:32 ` Tony Lindgren
2011-03-16 17:26 ` Aaro Koskinen
2011-03-16 17:10 ` Aaro Koskinen
2011-03-29 23:32 ` Tony Lindgren
2011-03-30 15:23 ` Kevin Hilman
2011-03-31 14:53 ` Aaro Koskinen
2011-04-02 2:42 ` Nicolas Pitre
2011-04-13 14:04 ` Tony Lindgren
2011-04-13 14:34 ` Aaro Koskinen
2011-04-15 13:41 ` Jarkko Nikula
2011-04-13 14:49 ` Nicolas Pitre
2011-04-13 15:09 ` Tony Lindgren
2011-04-19 10:13 ` Tony Lindgren
2011-04-19 13:27 ` Nicolas Pitre
2011-04-19 14:15 ` Tony Lindgren
2011-03-16 14:07 ` G, Manjunath Kondaiah [this message]
2011-03-16 14:20 ` G, Manjunath Kondaiah
2011-03-16 14:39 ` Kishore Kadiyala
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=20110316140710.GA10385@m-desktop \
--to=manjugk@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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.