linux-kernel - Re: [RFC PATCH 2/8] drm: exynos/dp: convert to drm bridge mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 6 Aug 2015 22:29:29 +0800
From:	Yakir Yang <ykk@...k-chips.com>
To:	Jingoo Han <jingoohan1@...il.com>,
	'Heiko Stuebner' <heiko@...ech.de>,
	'Russell King' <rmk+kernel@....linux.org.uk>,
	'Fabio Estevam' <fabio.estevam@...escale.com>,
	'Inki Dae' <inki.dae@...sung.com>
Cc:	djkurtz@...gle.com, dianders@...gle.com,
	'Takashi Iwai' <tiwai@...e.de>,
	'Andrzej Hajda' <a.hajda@...sung.com>,
	'Thierry Reding' <treding@...dia.com>,
	'Philipp Zabel' <p.zabel@...gutronix.de>,
	'David Airlie' <airlied@...ux.ie>,
	'Gustavo Padovan' <gustavo.padovan@...labora.co.uk>,
	'Seung-Woo Kim' <sw0312.kim@...sung.com>,
	'Kyungmin Park' <kyungmin.park@...sung.com>,
	'Krzysztof Kozlowski' <k.kozlowski@...sung.com>,
	'Kukjin Kim' <kgene@...nel.org>,
	'Ajay Kumar' <ajaykumar.rs@...sung.com>,
	'Joonyoung Shim' <jy0922.shim@...sung.com>,
	'Vincent Palatin' <vpalatin@...omium.org>,
	'Mark Yao' <mark.yao@...k-chips.com>,
	'Andy Yan' <andy.yan@...k-chips.com>,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	linux-samsung-soc@...r.kernel.org,
	linux-rockchip@...ts.infradead.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 2/8] drm: exynos/dp: convert to drm bridge mode

Hi Jingoo,

在 2015/8/6 22:19, Jingoo Han 写道:
> On Thursday, August 06, 2015 11:07 PM, Yakir Yang wrote:
>> In order to move exynos dp code to bridge directory,
>> we need to convert driver drm bridge mode first. As
>> dp driver already have a ptn3460 bridge, so we need
>> to move ptn bridge to the next bridge of dp bridge.
>>
>> Signed-off-by: Yakir Yang <ykk@...k-chips.com>
>> ---
>>   drivers/gpu/drm/exynos/exynos_dp_core.c | 196 ++++++++++++++++++++------------
>>   drivers/gpu/drm/exynos/exynos_dp_core.h |   2 +
>>   2 files changed, 126 insertions(+), 72 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/exynos/exynos_dp_core.c b/drivers/gpu/drm/exynos/exynos_dp_core.c
>> index a8097a4..aa99e23 100644
>> --- a/drivers/gpu/drm/exynos/exynos_dp_core.c
>> +++ b/drivers/gpu/drm/exynos/exynos_dp_core.c
>> @@ -3,6 +3,7 @@
>>    *
>>    * Copyright (C) 2012 Samsung Electronics Co., Ltd.
>>    * Author: Jingoo Han <jg1.han@...sung.com>
>> + *         Yakir Yang <ykk@...k-chips.com>
> Please don't add this.
> You just fixed some parts of this code. I don't find the reason
> why you have to be added to author for this file.
> If you want the title for an author, please send the patch
> for a new IP, instead of modifying the exiting codes.

Okay, thanks for your remind ;)

>>   [...]
>>   MODULE_AUTHOR("Jingoo Han <jg1.han@...sung.com>");
>> +MODULE_AUTHOR("Yakir Yang <ykk@...k-chips.com>");
> The same as above.

Done
>>   MODULE_DESCRIPTION("Samsung SoC DP Driver");
>>   MODULE_LICENSE("GPL v2");
>> diff --git a/drivers/gpu/drm/exynos/exynos_dp_core.h b/drivers/gpu/drm/exynos/exynos_dp_core.h
>> index c321ad5..f2584b8 100644
>> --- a/drivers/gpu/drm/exynos/exynos_dp_core.h
>> +++ b/drivers/gpu/drm/exynos/exynos_dp_core.h
>> @@ -3,6 +3,7 @@
>>    *
>>    * Copyright (C) 2012 Samsung Electronics Co., Ltd.
>>    * Author: Jingoo Han <jg1.han@...sung.com>
>> + *         Yakir Yang <ykk@...k-chips.com>
> The same as above.
> Here, you just added 1 line. If we add someone to author
> in this way, a lot of people should be added to author.

Done

- Yakir
> Best regards,
> Jingoo Han
>
>
>
>
>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/