public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Simon Horman <horms+renesas@verge.net.au>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Mikhail Ulyanov <mikhail.ulyanov@cogentembedded.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2] media: platform: rcar_jpu, sh_vou, vsp1: Use ARCH_RENESAS
Date: Wed, 2 Mar 2016 12:32:39 +0100	[thread overview]
Message-ID: <56D6CF57.2030507@xs4all.nl> (raw)
In-Reply-To: <1491869.T1zOZ4xfVB@avalon>

Hi Simon,

Note that the patch subject still mentions sh_vou.

Otherwise:

Acked-by: Hans Verkuil <hans.verkuil@cisco.com>

Regards,

	Hans

On 03/02/16 12:00, Laurent Pinchart wrote:
> Hi Simon,
> 
> Thank you for the patch.
> 
> On Wednesday 02 March 2016 10:14:51 Simon Horman wrote:
>> Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
>>
>> This is part of an ongoing process to migrate from ARCH_SHMOBILE to
>> ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
>> appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
>>
>> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> 
> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> 
>> ---
>> Based on media-tree/master
>>
>> v2
>> * Do not update VIDEO_SH_VOU to use ARCH_RENESAS as this is
>>   used by some SH-based platforms and is not used by any ARM-based platforms
>> so a dependency on ARCH_SHMOBILE is correct for that driver
>> * Added Geert Uytterhoeven's Ack
>> ---
>>  drivers/media/platform/Kconfig | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/media/platform/Kconfig b/drivers/media/platform/Kconfig
>> index 201f5c296a95..84e041c0a70e 100644
>> --- a/drivers/media/platform/Kconfig
>> +++ b/drivers/media/platform/Kconfig
>> @@ -238,7 +238,7 @@ config VIDEO_SH_VEU
>>  config VIDEO_RENESAS_JPU
>>  	tristate "Renesas JPEG Processing Unit"
>>  	depends on VIDEO_DEV && VIDEO_V4L2 && HAS_DMA
>> -	depends on ARCH_SHMOBILE || COMPILE_TEST
>> +	depends on ARCH_RENESAS || COMPILE_TEST
>>  	select VIDEOBUF2_DMA_CONTIG
>>  	select V4L2_MEM2MEM_DEV
>>  	---help---
>> @@ -250,7 +250,7 @@ config VIDEO_RENESAS_JPU
>>  config VIDEO_RENESAS_VSP1
>>  	tristate "Renesas VSP1 Video Processing Engine"
>>  	depends on VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API && HAS_DMA
>> -	depends on (ARCH_SHMOBILE && OF) || COMPILE_TEST
>> +	depends on (ARCH_RENESAS && OF) || COMPILE_TEST
>>  	select VIDEOBUF2_DMA_CONTIG
>>  	---help---
>>  	  This is a V4L2 driver for the Renesas VSP1 video processing engine.
> 

  reply	other threads:[~2016-03-02 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02  1:14 [PATCH v2] media: platform: rcar_jpu, sh_vou, vsp1: Use ARCH_RENESAS Simon Horman
2016-03-02 11:00 ` Laurent Pinchart
2016-03-02 11:32   ` Hans Verkuil [this message]
2016-03-03  0:25     ` Simon Horman
2016-03-02 13:17 ` Sergei Shtylyov

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=56D6CF57.2030507@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=horms+renesas@verge.net.au \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mchehab@osg.samsung.com \
    --cc=mikhail.ulyanov@cogentembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox