From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tony Lindgren <tony@atomide.com>,
hvaibhav@ti.com, linux-media@vger.kernel.org,
linux-omap@vger.kernel.org, Archit Taneja <archit@ti.com>
Subject: Re: [PATCH 0/2] omap_vout: remove cpu_is_* uses
Date: Thu, 29 Nov 2012 19:08:18 +0200 [thread overview]
Message-ID: <50B79682.1020305@ti.com> (raw)
In-Reply-To: <20121129150535.17ea00e9@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
On 2012-11-29 19:05, Mauro Carvalho Chehab wrote:
> Em Thu, 29 Nov 2012 17:39:45 +0100
> Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
>>> Please rather queue the cpu_is_omap removal to v3.8 so I can
>>> remove plat/cpu.h for omap2+.
>>
>> In that case the patches should go through the DSS tree. Mauro, are you fine
>> with that ?
>
> Sure.
>
> For both patches:
>
> Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Okay, thanks, I'll apply them to omapdss tree.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tony Lindgren <tony@atomide.com>, <hvaibhav@ti.com>,
<linux-media@vger.kernel.org>, <linux-omap@vger.kernel.org>,
Archit Taneja <archit@ti.com>
Subject: Re: [PATCH 0/2] omap_vout: remove cpu_is_* uses
Date: Thu, 29 Nov 2012 19:08:18 +0200 [thread overview]
Message-ID: <50B79682.1020305@ti.com> (raw)
In-Reply-To: <20121129150535.17ea00e9@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
On 2012-11-29 19:05, Mauro Carvalho Chehab wrote:
> Em Thu, 29 Nov 2012 17:39:45 +0100
> Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
>>> Please rather queue the cpu_is_omap removal to v3.8 so I can
>>> remove plat/cpu.h for omap2+.
>>
>> In that case the patches should go through the DSS tree. Mauro, are you fine
>> with that ?
>
> Sure.
>
> For both patches:
>
> Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Okay, thanks, I'll apply them to omapdss tree.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2012-11-29 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 13:33 [PATCH 0/2] omap_vout: remove cpu_is_* uses Tomi Valkeinen
2012-11-12 13:33 ` Tomi Valkeinen
2012-11-12 13:33 ` [PATCH 1/2] [media] omap_vout: use omapdss's version instead of cpu_is_* Tomi Valkeinen
2012-11-12 13:33 ` Tomi Valkeinen
2012-11-12 13:33 ` [PATCH 2/2] [media] omap_vout: remove extra include Tomi Valkeinen
2012-11-12 13:33 ` Tomi Valkeinen
2012-11-12 17:37 ` [PATCH 0/2] omap_vout: remove cpu_is_* uses Tony Lindgren
2012-11-28 15:13 ` Laurent Pinchart
2012-11-29 9:30 ` Tomi Valkeinen
2012-11-29 9:30 ` Tomi Valkeinen
2012-11-29 9:36 ` Laurent Pinchart
2012-11-29 16:29 ` Tony Lindgren
2012-11-29 16:39 ` Laurent Pinchart
2012-11-29 17:05 ` Mauro Carvalho Chehab
2012-11-29 17:08 ` Tomi Valkeinen [this message]
2012-11-29 17:08 ` Tomi Valkeinen
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=50B79682.1020305@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=hvaibhav@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@redhat.com \
--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.