linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org,
	Mauro Carvalho Chehab <m.chehab@samsung.com>,
	LMML <linux-media@vger.kernel.org>
Subject: Re: [PATCH 16/17] [media] exynos4-is: removes s5pc100 related fimc codes
Date: Mon, 30 Jun 2014 16:03:02 +0200	[thread overview]
Message-ID: <53B16E16.7080200@samsung.com> (raw)
In-Reply-To: <1404163947-3105-17-git-send-email-kgene.kim@samsung.com>

On 30/06/14 23:32, Kukjin Kim wrote:
> This patch removes s5pc100 related fimc codes because of no more support
> S5PC100 SoC in mainline.

I have applied this patch to my tree. It's also fine if you would like to
merge the whole series together. In such case feel free to add:

Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>

Please let me know if you want me to drop this patch from the media tree.

--
Regards,
Sylwester

> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
> Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>
> ---
>  Documentation/video4linux/fimc.txt            |    2 +-
>  drivers/media/platform/exynos4-is/fimc-core.c |   15 ---------------
>  2 files changed, 1 insertion(+), 16 deletions(-)
> 
> diff --git a/Documentation/video4linux/fimc.txt b/Documentation/video4linux/fimc.txt
> index e0c6b8b..1441fcf 100644
> --- a/Documentation/video4linux/fimc.txt
> +++ b/Documentation/video4linux/fimc.txt
> @@ -15,7 +15,7 @@ drivers/media/platform/exynos4-is directory.
>  1. Supported SoCs
>  =================
>  
> -S5PC100 (mem-to-mem only), S5PV210, EXYNOS4210
> +S5PV210, EXYNOS4210
>  
>  2. Supported features
>  =====================
> diff --git a/drivers/media/platform/exynos4-is/fimc-core.c b/drivers/media/platform/exynos4-is/fimc-core.c
> index b70fd99..5c800b4 100644
> --- a/drivers/media/platform/exynos4-is/fimc-core.c
> +++ b/drivers/media/platform/exynos4-is/fimc-core.c
> @@ -1204,18 +1204,6 @@ static const struct fimc_variant fimc2_variant_s5pv210 = {
>  	.pix_limit	 = &s5p_pix_limit[2],
>  };
>  
> -/* S5PC100 */
> -static const struct fimc_drvdata fimc_drvdata_s5p = {
> -	.variant = {
> -		[0] = &fimc0_variant_s5p,
> -		[1] = &fimc0_variant_s5p,
> -		[2] = &fimc2_variant_s5p,
> -	},
> -	.num_entities	= 3,
> -	.lclk_frequency = 133000000UL,
> -	.out_buf_count	= 4,
> -};
> -
>  /* S5PV210, S5PC110 */
>  static const struct fimc_drvdata fimc_drvdata_s5pv210 = {
>  	.variant = {
> @@ -1251,9 +1239,6 @@ static const struct fimc_drvdata fimc_drvdata_exynos4x12 = {
>  
>  static const struct platform_device_id fimc_driver_ids[] = {
>  	{
> -		.name		= "s5p-fimc",
> -		.driver_data	= (unsigned long)&fimc_drvdata_s5p,
> -	}, {
>  		.name		= "s5pv210-fimc",
>  		.driver_data	= (unsigned long)&fimc_drvdata_s5pv210,
>  	}, {


           reply	other threads:[~2014-06-30 14:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1404163947-3105-17-git-send-email-kgene.kim@samsung.com>]

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=53B16E16.7080200@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.chehab@samsung.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;
as well as URLs for NNTP newsgroup(s).