Samsung defconfig update for v3.14
The following changes since commit 54b56e62d20ac0de6e8e12b7efdaf3a1b9b6541c:
ARM: exynos_defconfig: increase CONFIG_NR_CPUS value to 8 (2013-12-02
07:33:38 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
tags/samsung-defconfig-2
for you to fetch changes up to 7c7be272ae6413d1dd298e68752f5e34bc9b3eba:
ARM: exynos_defconfig: Enable S2MPS11 voltage regulator (2013-12-21
06:27:47 +0900)
----------------------------------------------------------------
Samsung defconfig 2nd update for v3.14
- enable REGULATOR S2MPS11 for Arndale Octa board
----------------------------------------------------------------
Sachin Kamat (1):
ARM: exynos_defconfig: Enable S2MPS11 voltage regulator
arch/arm/configs/exynos_defconfig | 1 + 1 file changed, 1 insertion(+)
Quoted 8 lines · Kukjin Kim
The following changes since commit
54b56e62d20ac0de6e8e12b7efdaf3a1b9b6541c:ARM:
exynos_defconfig: increaseCONFIG_NR_CPUSvalue to 8
(2013-12-02 07:33:38 +0900)are available in the git repository at:
Quoted 7 lines
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
tags/samsung-defconfig-2for you to fetch changes up to
7c7be272ae6413d1dd298e68752f5e34bc9b3eba:ARM:
exynos_defconfig: Enable S2MPS11 voltage regulator
(2013-12-21 06:27:47 +0900)
Pulled into next/boards. Thanks!
-Olof
Quoted 12 lines · Olof Johansson
Quoted 11 lines · Kukjin Kim
The following changes since commit
54b56e62d20ac0de6e8e12b7efdaf3a1b9b6541c:ARM:
exynos_defconfig: increaseCONFIG_NR_CPUSvalue to 8
(2013-12-02 07:33:38 +0900)are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
tags/samsung-defconfig-2
Quoted 6 lines
Quoted 4 lines
for you to fetch changes up to
7c7be272ae6413d1dd298e68752f5e34bc9b3eba:ARM:
exynos_defconfig: Enable S2MPS11 voltage regulator
(2013-12-21 06:27:47 +0900)Pulled into next/boards. Thanks!
The regulator driver causes build breaks. Really, nobody checks these things before sending patches or merge requests?
Having exynos_defconfig broken in arm-soc isn't an alternative. So I dropped this branch again. If the regulator driver gets fixed in -rc then we can probably merge it before the merge window, otherwise we'll have to merge the defconfig change after the regulator fix goes in for the 3.14 merge window.
-Olof
Quoted 20 lines · Olof Johansson
Quoted 12 lines · Olof Johansson
Quoted 11 lines · Kukjin Kim
The following changes since commit
54b56e62d20ac0de6e8e12b7efdaf3a1b9b6541c:ARM:
exynos_defconfig: increaseCONFIG_NR_CPUSvalue to 8
(2013-12-02 07:33:38 +0900)are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
tags/samsung-defconfig-2Quoted 6 lines
Quoted 4 lines
for you to fetch changes up to
7c7be272ae6413d1dd298e68752f5e34bc9b3eba:ARM:
exynos_defconfig: Enable S2MPS11 voltage regulator
(2013-12-21 06:27:47 +0900)Pulled into next/boards. Thanks!
Quoted 8 lines
The regulator driver causes build breaks. Really, nobody checks these things before sending patches or merge requests?
Having
exynos_defconfigbroken in arm-soc isn't an alternative. So I dropped this branch again. If the regulator driver gets fixed in -rc then we can probably merge it before the merge window, otherwise we'll have to merge the defconfig change after the regulator fix goes in for the 3.14 merge window.
Ah, I guess the fix went in after -rc4, which is the latest -rc that we have in for-next today. I'll bring for-next forward and merge this in.
Still, it's odd that you were able to test your branch before sending it in.
-Olof
Quoted 11 lines · Olof Johansson
Quoted 8 lines · Olof Johansson
The regulator driver causes build breaks. Really, nobody checks these things before sending patches or merge requests?
Having
exynos_defconfigbroken in arm-soc isn't an alternative. So I dropped this branch again. If the regulator driver gets fixed in -rc then we can probably merge it before the merge window, otherwise we'll have to merge the defconfig change after the regulator fix goes in for the 3.14 merge window.
Quoted 5 lines
Ah, I guess the fix went in after -rc4, which is the latest -rc that we have in for-next today. I'll bring for-next forward and merge this in.
Still, it's odd that you were able to test your branch before sending it in.
The build breakage was only introduced in -rc4 - a MFD/RTC change went
in via Andrew's tree so it got no exposure in -next before it showed up
in Linus' tree which wasn't good. The fix was in by -rc5, looking at
the date on the pull request I expect that any testing against -next (as
opposed to arm-soc) would've been OK and since the branch is based on
-rc1 it'd have tested out by itself as well.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131231/7a685a90/attachment.sig>
Quoted 16 lines · Mark Brown
Quoted 14 lines · Olof Johansson
Quoted 8 lines · Olof Johansson
The regulator driver causes build breaks. Really, nobody checks these things before sending patches or merge requests?
Having
exynos_defconfigbroken in arm-soc isn't an alternative. So I dropped this branch again. If the regulator driver gets fixed in -rc then we can probably merge it before the merge window, otherwise we'll have to merge the defconfig change after the regulator fix goes in for the 3.14 merge window.Ah, I guess the fix went in after -rc4, which is the latest -rc that we have in for-next today. I'll bring for-next forward and merge this in.
Quoted 8 lines
Quoted 1 line
Still, it's odd that you were able to test your branch before sending it in.
The build breakage was only introduced in -rc4 - a MFD/RTC change went in via Andrew's tree so it got no exposure in -next before it showed up in Linus' tree which wasn't good. The fix was in by -rc5, looking at the date on the pull request I expect that any testing against -next (as opposed to arm-soc) would've been OK and since the branch is based on -rc1 it'd have tested out by itself as well.
Ah, yeah, that explains it. Thanks for the clarification.
-Olof
Quoted 31 lines · Olof Johansson
Quoted 9 lines · Mark Brown
Quoted 8 lines · Olof Johansson
Quoted 6 lines · Olof Johansson
The regulator driver causes build breaks. Really, nobody checks these things before sending patches or merge requests?
Having
exynos_defconfigbroken in arm-soc isn't an alternative. So I dropped this branch again. If the regulator driver gets fixed in -rc then we can probably merge it before the merge window, otherwisewe'll
Quoted 1 line
Quoted 1 line
Quoted 1 line
have to merge the defconfig change after the regulator fix goes in
for
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
the 3.14 merge window.
Ah, I guess the fix went in after -rc4, which is the latest -rc that we have in for-next today. I'll bring for-next forward and merge this in.
Still, it's odd that you were able to test your branch before sending
it in.
Quoted 7 lines
The build breakage was only introduced in -rc4 - a MFD/RTC change went in via Andrew's tree so it got no exposure in -next before it showed up in Linus' tree which wasn't good. The fix was in by -rc5, looking at the date on the pull request I expect that any testing against -next (as opposed to arm-soc) would've been OK and since the branch is based on -rc1 it'd have tested out by itself as well.
Quoted 2 lines
Ah, yeah, that explains it. Thanks for the clarification.
Sorry for late response and Mark, thanks for your response ;-)
Olof, I have not seen regarding problem in my tree before my pull-request so I didn't know but I will look at -next and arm-soc more closely.
Thanks.
Kukjin