On Tue, Jun 20, 2017 at 11:53 AM, Emil Velikov wrote:
> On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
>> Although header is included only once but still having an include guard
>> is a good practice. To avoid confusion, add SoC prefix to existing
>> Exynos5433 header include guard.
>>
>>
On Tue, Jun 20, 2017 at 12:57 PM, Emil Velikov wrote:
> On 20 June 2017 at 11:02, Krzysztof Kozlowski wrote:
>> On Tue, Jun 20, 2017 at 11:53 AM, Emil Velikov
>> wrote:
>>> On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
Although header is included only once but still having an inclu
On 20 June 2017 at 11:02, Krzysztof Kozlowski wrote:
> On Tue, Jun 20, 2017 at 11:53 AM, Emil Velikov
> wrote:
>> On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
>>> Although header is included only once but still having an include guard
>>> is a good practice. To avoid confusion, add SoC
On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
> Although header is included only once but still having an include guard
> is a good practice. To avoid confusion, add SoC prefix to existing
> Exynos5433 header include guard.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> include/video/exy
Although header is included only once but still having an include guard
is a good practice. To avoid confusion, add SoC prefix to existing
Exynos5433 header include guard.
Signed-off-by: Krzysztof Kozlowski
---
include/video/exynos5433_decon.h | 6 +++---
include/video/exynos7_decon.h| 5 ++
