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:	Tue, 25 Mar 2014 06:32:04 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Alex Shi <alex.shi@...aro.org>, mark.hambleton@...adcom.com,
	mark.brown@...aro.org, eduardo.valentin@...com, mporter@...aro.org,
	lsk-interest@...aro.org, linaro-kernel@...aro.org
CC:	Jean Delvare <khali@...ux-fr.org>, linux-kernel@...r.kernel.org,
	lm-sensors@...sensors.org
Subject: Re: [lm-sensors] [PATCH 07/19] hwmon: lm75: expose to thermal fw
 via DT nodes

On 03/25/2014 03:49 AM, Alex Shi wrote:
> From: Eduardo Valentin <eduardo.valentin@...com>
>
> This patch adds to lm75 temperature sensor the possibility
> to expose itself as thermal zone device, registered on the
> thermal framework.
>
> The thermal zone is built only if a device tree node
> describing a thermal zone for this sensor is present
> inside the lm75 DT node. Otherwise, the driver behavior
> will be the same.
>
> Note: This patch has also been reviewed by Jean D. He has
> requested to perform a wider inspection of possible
> users of thermal and hwmon interaction API. On the other
> hand, the change on this patch is acceptable on first
> step of overall code change.
>
> Cc: Jean Delvare <khali@...ux-fr.org>
> Cc: lm-sensors@...sensors.org
> Cc: linux-kernel@...r.kernel.org
> Acked-by: Guenter Roeck <linux@...ck-us.net>
> Signed-off-by: Eduardo Valentin <eduardo.valentin@...com>
> (cherry picked from commit 22e731838b0e337fed5f16c67aa0b954028dfe93)
>
> Signed-off-by: Alex Shi <alex.shi@...aro.org>

Not entirely sure why you are sending this patch to a public list.
This patch as well as patch 8/19 have already been applied.
Ok, it appears that you plan to apply it to some other branch.
So what ?

Can you clarify ?

Reason for asking is that I don't want to get flooded with e-mail
each time someone applies a patch to some arbitrary branch,
and I end up being confused and looking through the code
trying to figure out what is going on. Whatever it is, your branch
isn't that special that you need to tell the rest of the world
what you are doing.

Thanks,
Guenter

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