[PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-03-07 Thread Inki Dae
Shim; sunil joshi > Subject: Re: [PATCH] drm/exynos: modify the compatible string for exynos > fimd > > Hi Mr Inki Dae, > > On 28 February 2013 08:12, Joonyoung Shim wrote: > > On 02/27/2013 07:32 PM, Vikas Sajjan wrote: > >> > >> modified compatible string

[PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-03-07 Thread Vikas Sajjan
.org; linux-media at vger.kernel.org; >> kgene.kim at samsung.com; Joonyoung Shim; sunil joshi >> Subject: Re: [PATCH] drm/exynos: modify the compatible string for exynos >> fimd >> >> Hi Mr Inki Dae, >> >> On 28 February 2013 08:12, Joonyoung Shim wrote: &g

[PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-03-07 Thread Vikas Sajjan
Hi Mr Inki Dae, On 28 February 2013 08:12, Joonyoung Shim wrote: > On 02/27/2013 07:32 PM, Vikas Sajjan wrote: >> >> modified compatible string for exynos4 fimd as "exynos4210-fimd" and >> exynos5 fimd as "exynos5250-fimd" to stick to the rule that compatible >> value should be named after first

Re: [PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-03-07 Thread Vikas Sajjan
Hi Mr Inki Dae, On 28 February 2013 08:12, Joonyoung Shim jy0922.s...@samsung.com wrote: On 02/27/2013 07:32 PM, Vikas Sajjan wrote: modified compatible string for exynos4 fimd as exynos4210-fimd and exynos5 fimd as exynos5250-fimd to stick to the rule that compatible value should be named

Re: [PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-03-07 Thread Vikas Sajjan
@samsung.com; Joonyoung Shim; sunil joshi Subject: Re: [PATCH] drm/exynos: modify the compatible string for exynos fimd Hi Mr Inki Dae, On 28 February 2013 08:12, Joonyoung Shim jy0922.s...@samsung.com wrote: On 02/27/2013 07:32 PM, Vikas Sajjan wrote: modified compatible string

RE: [PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-03-06 Thread Inki Dae
] drm/exynos: modify the compatible string for exynos fimd Hi Mr Inki Dae, On 28 February 2013 08:12, Joonyoung Shim jy0922.s...@samsung.com wrote: On 02/27/2013 07:32 PM, Vikas Sajjan wrote: modified compatible string for exynos4 fimd as exynos4210-fimd and exynos5 fimd as exynos5250

[PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-02-28 Thread Joonyoung Shim
On 02/27/2013 07:32 PM, Vikas Sajjan wrote: > modified compatible string for exynos4 fimd as "exynos4210-fimd" and > exynos5 fimd as "exynos5250-fimd" to stick to the rule that compatible > value should be named after first specific SoC model in which this > particular IP version was included as

[PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-02-28 Thread Vikas Sajjan
Thanks Mr. Shim. On 28 February 2013 08:12, Joonyoung Shim wrote: > On 02/27/2013 07:32 PM, Vikas Sajjan wrote: >> >> modified compatible string for exynos4 fimd as "exynos4210-fimd" and >> exynos5 fimd as "exynos5250-fimd" to stick to the rule that compatible >> value should be named after

Re: [PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-02-28 Thread Vikas Sajjan
Thanks Mr. Shim. On 28 February 2013 08:12, Joonyoung Shim jy0922.s...@samsung.com wrote: On 02/27/2013 07:32 PM, Vikas Sajjan wrote: modified compatible string for exynos4 fimd as exynos4210-fimd and exynos5 fimd as exynos5250-fimd to stick to the rule that compatible value should be named

[PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-02-27 Thread Vikas Sajjan
modified compatible string for exynos4 fimd as "exynos4210-fimd" and exynos5 fimd as "exynos5250-fimd" to stick to the rule that compatible value should be named after first specific SoC model in which this particular IP version was included as discussed at

[PATCH] drm/exynos: modify the compatible string for exynos fimd

2013-02-27 Thread Vikas Sajjan
modified compatible string for exynos4 fimd as exynos4210-fimd and exynos5 fimd as exynos5250-fimd to stick to the rule that compatible value should be named after first specific SoC model in which this particular IP version was included as discussed at https://patchwork.kernel.org/patch/2144861/