From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>, Kevin Hilman <khilman@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Code for v2.6.39 merge window frozen, patches archived
Date: Tue, 15 Mar 2011 08:35:44 +0530 [thread overview]
Message-ID: <4D7ED788.90307@ti.com> (raw)
In-Reply-To: <20110314192538.GH7258@atomide.com>
Tony Lindgren wrote, on 03/15/2011 12:55 AM:
[..]
> 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.
Guess it is too late, but am curious:
http://marc.info/?l=linux-omap&m=129933897910785&w=2
Why has it been dropped from .39(aka archived out)? I dont see any
review comments to the contrary from any maintainers explaining why we
should'nt take it.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2011-03-15 3:05 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 [this message]
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
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=4D7ED788.90307@ti.com \
--to=nm@ti.com \
--cc=khilman@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.