linux-kernel - Re: [PATCH v2] mfd: asic3: Set DS1WM clock

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20120416160433.GK24130@sortiz-mobl>
Date:	Mon, 16 Apr 2012 18:04:33 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Paul Parsons <lost.distance@...oo.com>
Cc:	linux-kernel@...r.kernel.org, philipp.zabel@...il.com
Subject: Re: [PATCH v2] mfd: asic3: Set DS1WM clock_rate

Hi Paul,

On Mon, Apr 09, 2012 at 01:18:31PM +0100, Paul Parsons wrote:
> The mfd/asic3 driver does not set the ds1wm_driver_data clock_rate field
> before passing the structure to the DS1WM w1 busmaster driver.
> This was not noticed before commit 26a6afb, because ds1wm_find_divisor()
> unintentionally returned the correct divisor when a zero clock_rate was
> passed in. However after that commit DS1WM fails a zero clock_rate:
> 
> ds1wm ds1wm: no suitable divisor for 0Hz clock
> 
> This patch sets the ds1wm_driver_data clock_rate field.
> 
> Signed-off-by: Paul Parsons <lost.distance@...oo.com>
> Cc: Philipp Zabel <philipp.zabel@...il.com>
> ---
> 
> V2:
> Separated arch/arm/mach-pxa/hx4700.c changes into a separate patch,
> to avoid crossing maintainer boundaries.
> This patch now submitted to linux-kernel instead of linux-arm-kernel.
> Rebased from linux-3.0.1 to linux-3.4-rc2.
> 
>  drivers/mfd/asic3.c       |    9 ++++++---
>  include/linux/mfd/asic3.h |    2 ++
>  2 files changed, 8 insertions(+), 3 deletions(-)
Thanks, patch applied.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/