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] [day] [month] [year] [list]
Date:	Fri, 13 Jul 2012 13:56:44 +0200
From:	Lee Jones <lee.jones@...aro.org>
To:	Rajanikanth HV <rajanikanth.hv@...ricsson.com>
CC:	"linaro-dev-request@...ts.linaro.org" 
	<linaro-dev-request@...ts.linaro.org>,
	"linaro-dev@...ts.linaro.org" <linaro-dev@...ts.linaro.org>,
	STEricsson_nomadik_linux@...t.st.com, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, patches@...aro.org
Subject: Re: [PATCH] mfd: Implement devicetree support for AB8500 Btemp

>>> @@ -964,11 +966,13 @@ static int __devinit ab8500_btemp_probe(struct platform_device *pdev)
>>>    {
>>>        int irq, i, ret = 0;
>>>        u8 val;
>>> -     struct abx500_bm_plat_data *plat_data = pdev->dev.platform_data;
>>
>> I already told you about this.
> your previous comment was: "No, it's meant to work with _both_ platform
> and Device Tree registation."

Right.

> Why is this required when platform specific information/file is removed?

It's not being removed, it's just not allowed to be upstreamed. Once we 
enforce Device Tree only booting, we'll go round and remove that 
capability from the drivers. Until then, you must ensure all Device Tree 
enablement works in parallel with platform registration.

Concentrate on enabling the drivers for DT for now and we'll extract 
platform data support later.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
M: +44 77 88 633 515
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog


--
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