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:	Tue, 29 May 2012 16:29:21 +0800
From:	Lee Jones <lee.jones@...aro.org>
To:	axel.lin@...il.com
CC:	linux-kernel@...r.kernel.org, Samuel Ortiz <sameo@...ux.intel.com>,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH] mfd: Remove config AB8500_I2C_CORE Kconfig entry

On 29/05/12 15:53, Axel Lin wrote:
> 2012/5/29 Lee Jones<lee.jones@...aro.org>:
>> On 29/05/12 14:19, Axel Lin wrote:
>>>
>>> config AB8500_I2C_CORE is not used after commit d28f1db
>>> "mfd: Remove confusing ab8500-i2c file and merge into ab8500-core".
>>> Thus remove it.
>>>
>>> Signed-off-by: Axel Lin<axel.lin@...il.com>
>>
>>
>> I have this patch embedded into a patch-set I'm going to send to ARM-SoC for
>> inclusion into -rc1 this afternoon. Would you mind leaving this one?
>
> I don't mind.
> But AFAIK, commit d28f1db is in mfd tree.
> Any reason you want to send the patch to ARM-SoC instead of mfd tree.

I don't actually have a preference as to which tree it goes into, so 
long as it's sent to Mainline on or before -rc1. This patch isn't too 
important, but the others in the patch-set are and I'd like to keep them 
together if possible. Unless of course Sam or Mark have any issues with 
that. In which case I will bow down to them and do as they wish.

Kind regards,
Lee

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