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]
Message-ID: <54938C81.6070304@freescale.com>
Date:	Fri, 19 Dec 2014 10:25:05 +0800
From:	Liu Ying <Ying.Liu@...escale.com>
To:	Philipp Zabel <p.zabel@...gutronix.de>
CC:	<dri-devel@...ts.freedesktop.org>, <devicetree@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <linux@....linux.org.uk>,
	<kernel@...gutronix.de>, <thierry.reding@...il.com>,
	<shawn.guo@...aro.org>, <mturquette@...aro.org>,
	<airlied@...ux.ie>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC v2 06/14] ARM: dts: imx6qdl: Move existing MIPI DSI
 ports into a new 'ports' node

Hi Philipp,

On 12/18/2014 06:33 PM, Philipp Zabel wrote:
> Am Donnerstag, den 18.12.2014, 15:11 +0800 schrieb Liu Ying:
>> The MIPI DSI node contains some ports which represent possible DRM CRTCs
>> it can connect with.  Each port has a 'reg' property embedded.  This
>> property will be wrongly interpretted by the MIPI DSI bus driver, because
>> the driver will take each subnode which contains a 'reg' property as a
>> DSI peripheral device.  This patch moves the existing MIPI DSI ports into
>> a new 'ports' node so that the MIPI DSI bus driver may distinguish its
>> DSI peripheral device(s) from the existing ports.
>>
>> Signed-off-by: Liu Ying <Ying.Liu@...escale.com>
>
> Acked-by: Philipp Zabel <p.zabel@...gutronix.de>

Thanks.  I'll add your ack for this one in the next version.

Regards,
Liu Ying

>
> regards
> Philipp
>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ