linux-kernel - Re: [PATCH 5/5] mfd: arizona: Lower ARIZONA_MAX_CORE

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: <20140617143648.GF29841@lee--X1>
Date:	Tue, 17 Jun 2014 15:36:48 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	sameo@...ux.intel.com, patches@...nsource.wolfsonmicro.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] mfd: arizona: Lower ARIZONA_MAX_CORE_SUPPLIES to 2

On Mon, 02 Jun 2014, Charles Keepax wrote:

> There are no Arizona devices with 3 core supplies but we define a fix
> array with space for 3 core supplies. Lower the ARIZONA_MAX_CORE_SUPPLIES
> define to 2, to save a few bytes.
> 
> Signed-off-by: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
> ---
>  include/linux/mfd/arizona/core.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Applied, thanks.

> diff --git a/include/linux/mfd/arizona/core.h b/include/linux/mfd/arizona/core.h
> index 6acb058..2bf1d74 100644
> --- a/include/linux/mfd/arizona/core.h
> +++ b/include/linux/mfd/arizona/core.h
> @@ -18,7 +18,7 @@
>  #include <linux/regulator/consumer.h>
>  #include <linux/mfd/arizona/pdata.h>
>  
> -#define ARIZONA_MAX_CORE_SUPPLIES 3
> +#define ARIZONA_MAX_CORE_SUPPLIES 2
>  
>  enum arizona_type {
>  	WM5102 = 1,

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
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/