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: <05ed01cdfde8$b529fc00$1f7df400$@samsung.com>
Date:	Mon, 28 Jan 2013 22:20:15 -0800
From:	Kukjin Kim <kgene.kim@...sung.com>
To:	'Sachin Kamat' <sachin.kamat@...aro.org>,
	'Linus Walleij' <linus.walleij@...aro.org>
Cc:	'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

Sachin Kamat wrote:
> 
> Hi Linus, Kukjin,
> 
> Patch titled "pinctrl: exynos: change PINCTRL_EXYNOS option"
> (linux-next commit Id: 7452b64d) which is present in linux-next is
> missing in the mainline kernel. 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:
> 
>  WARNING: at drivers/gpio/gpio-samsung.c:3102
> samsung_gpiolib_init+0x29c/0x2e8()
>  Unknown SoC in gpio-samsung, no GPIOs added
>  Modules linked in:
>  [<c00142dc>] (unwind_backtrace+0x0/0xf8) from [<c00202bc>]
> (warn_slowpath_common+0x4c/0x64)
>  [<c00202bc>] (warn_slowpath_common+0x4c/0x64) from [<c0020368>]
> (warn_slowpath_fmt+0x30/0x40)
>  [<c0020368>] (warn_slowpath_fmt+0x30/0x40) from [<c028b924>]
> (samsung_gpiolib_init+0x29c/0x2e8)
>  [<c028b924>] (samsung_gpiolib_init+0x29c/0x2e8) from [<c000862c>]
> (do_one_initcall+0x34/0x174)
>  [<c000862c>] (do_one_initcall+0x34/0x174) from [<c0275960>]
> (kernel_init_freeable+0xfc/0x1c8)
>  [<c0275960>] (kernel_init_freeable+0xfc/0x1c8) from [<c01c0a5c>]
> (kernel_init+0x8/0xe4)
>  [<c01c0a5c>] (kernel_init+0x8/0xe4) from [<c000e158>]
> (ret_from_fork+0x14/0x3c)
> 
Sachin, thanks for your information.

Linus, can you check following again?

https://lkml.org/lkml/2013/1/18/461

Thanks.

- Kukjin


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