From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] omap display subsystem changes for 2.6.39
Date: Mon, 28 Mar 2011 21:07:27 +0000 [thread overview]
Message-ID: <20110328210727.GF30616@atomide.com> (raw)
In-Reply-To: <1300866362.2613.5.camel@deskari>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [110323 00:43]:
> On Tue, 2011-03-22 at 13:49 -0500, Felipe Contreras wrote:
> > On Mon, Mar 21, 2011 at 11:51 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > > Here are OMAP display subsystem patches for 2.6.39 merge window. Quite a
> > > bit of them, and many changes also in arch/arm/mach-omap2, which
> > > unfortunately couldn't go through Tony's linux-omap tree due to
> > > dependencies on DSS driver code.
> >
> > What about this one?
> > http://article.gmane.org/gmane.linux.ports.arm.omap/44975
>
> I seem to have missed that one. But I think that should go through
> Tony's tree to avoid conflicts. Tony?
>
> Acked-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Seems OK for -rc cycle.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] omap display subsystem changes for 2.6.39
Date: Mon, 28 Mar 2011 14:07:27 -0700 [thread overview]
Message-ID: <20110328210727.GF30616@atomide.com> (raw)
In-Reply-To: <1300866362.2613.5.camel@deskari>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [110323 00:43]:
> On Tue, 2011-03-22 at 13:49 -0500, Felipe Contreras wrote:
> > On Mon, Mar 21, 2011 at 11:51 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > > Here are OMAP display subsystem patches for 2.6.39 merge window. Quite a
> > > bit of them, and many changes also in arch/arm/mach-omap2, which
> > > unfortunately couldn't go through Tony's linux-omap tree due to
> > > dependencies on DSS driver code.
> >
> > What about this one?
> > http://article.gmane.org/gmane.linux.ports.arm.omap/44975
>
> I seem to have missed that one. But I think that should go through
> Tony's tree to avoid conflicts. Tony?
>
> Acked-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Seems OK for -rc cycle.
Tony
next prev parent reply other threads:[~2011-03-28 21:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 9:51 [GIT PULL] omap display subsystem changes for 2.6.39 Tomi Valkeinen
2011-03-21 9:51 ` Tomi Valkeinen
2011-03-21 13:05 ` Tomi Valkeinen
2011-03-21 13:05 ` Tomi Valkeinen
2011-03-21 17:43 ` John S
2011-03-21 17:55 ` John S
2011-03-21 18:17 ` Tomi Valkeinen
2011-03-21 18:17 ` Tomi Valkeinen
2011-03-22 5:40 ` Paul Mundt
2011-03-22 5:40 ` Paul Mundt
2011-03-22 5:55 ` Tomi Valkeinen
2011-03-22 5:55 ` Tomi Valkeinen
2011-03-22 18:49 ` Felipe Contreras
2011-03-22 18:49 ` Felipe Contreras
2011-03-23 7:46 ` Tomi Valkeinen
2011-03-23 7:46 ` Tomi Valkeinen
2011-03-28 21:07 ` Tony Lindgren [this message]
2011-03-28 21:07 ` 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=20110328210727.GF30616@atomide.com \
--to=tony@atomide.com \
--cc=felipe.contreras@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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.