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:	Fri, 25 Jul 2014 13:52:00 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	"Zhang, Rui" <rui.zhang@...el.com>,
	"eduardo.valentin@...il.com" <eduardo.valentin@...il.com>
CC:	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] thermal: of: look for sensor driver parent node if device
 node missing

Thanks Rui.
It seems I have put the wrong email-id for Eduardo (which I got from 
get_maintainer) and the original patch not reached to Eduardo.

Do I need to re-post patch?

Thanks,
Laxman

On Thursday 24 July 2014 08:45 PM, Zhang, Rui wrote:
> Hi, Laxman,
>
> As Eduardo is the of thermal author and maintainer, I will take your patch only if you can get ACK from Eduardo.
>
> Eduardo,
> Do you have any comments on this?
>
> Thanks,
> rui
>
>> -----Original Message-----
>> From: Laxman Dewangan [mailto:ldewangan@...dia.com]
>> Sent: Thursday, July 24, 2014 5:49 PM
>> To: Zhang, Rui; eduardo.valentin@...com
>> Cc: linux-pm@...r.kernel.org; linux-kernel@...r.kernel.org
>> Subject: Re: [PATCH] thermal: of: look for sensor driver parent node if
>> device node missing
>> Importance: High
>>
>> On Monday 14 July 2014 04:42 PM, Laxman Dewangan wrote:
>>> There are some mfd devices which supports junction thermal interrupt
>>> like ams,AS3722. The DT binding of these devices are defined as the
>>> flat and drivers for sub module of such devices are registered as the
>>> mfd_add_devices. In this method, the sub devices registered as
>>> platform driver and these do not have the of_node pointer on their
>>> device structure. In this case, use the parent of_node pointer to get
>>> the required of_node pointer.
>>>
>> Any comment please?

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