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:	Thu, 31 Jan 2013 14:59:08 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Sachin Kamat <sachin.kamat@...aro.org>
Cc:	Kukjin Kim <kgene.kim@...sung.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-samsung-soc <linux-samsung-soc@...r.kernel.org>
Subject: Re: Failure due to missing (Exynos related) pinctrl patch

On Wed, Jan 30, 2013 at 11:15 AM, Sachin Kamat <sachin.kamat@...aro.org> wrote:
> On 30 January 2013 15:18, Linus Walleij <linus.walleij@...aro.org> wrote:
>> On Wed, Jan 30, 2013 at 5:08 AM, Kukjin Kim <kgene.kim@...sung.com> wrote:
>>> Sachin Kamat wrote:
>>>>
>>>> >> This patch is required along with the
>>>> >> patch "gpio: samsung: fix pinctrl condition for exynos and exynos5440"
>>>> >> (mainline commit Id: e4a5da51) which has already made it into
>>>> >> mainline. Without the missing patch we get the following boot up
>>>> >> warnings and subsequent failures with dt boot on 4412 based board:
>>>> >
>>>> > Hm I didn't realize there was a dependency between these
>>>> > patches, oh well, better get the pull for the pinctrl tree finished
>>>> > off then...
>
>>
>> Torvalds has already pulled it in -> problem solved. :-)
>>
>
> I tested this on Linus T.'s latest tip (2e51b231) and the problem
> still persists :(
>
> You sent the following patch in your pull request to Linus T.:
> Kukjin Kim (1):
>       pinctrl: samsung: removing duplicated condition for PINCTRL_SAMSUNG
>
> However, the missing dependent patch is:
>
> "pinctrl: exynos: change PINCTRL_EXYNOS option"

Aha how typically chaotical.

And that is in the middle of the devel branch that people are
basing their development on.

Not much to do, I cherry-picked that patch to the fixes branch
and hope that git will cope. (It usually does.)

Yours,
Linus Walleij
--
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