mbox

[GIT,PULL] Samsung fixes for v4.3

Message ID 1443571154-28722-1-git-send-email-k.kozlowski@samsung.com
State New
Headers show

Pull-request

https://github.com/krzk/linux.git tags/samsung-fixes-4.3

Message

Krzysztof Kozlowski Sept. 29, 2015, 11:59 p.m. UTC
Dear Kukjin,

Below you will find fixes for current release cycle which are not
present yet in your tree.

Best regards,
Krzysztof


The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:

  Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)

are available in the git repository at:

  https://github.com/krzk/linux.git tags/samsung-fixes-4.3

for you to fetch changes up to c7d2ecd9f64c351cb4d551f1f472d0fc09c3cae8:

  ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420 (2015-09-29 15:39:58 +0900)

----------------------------------------------------------------
Fixes for Exynos (DT and mach code):
1. Finally fix booting of all 8 cores on Exynos Octa (Exynos542x): all
   8 cores are booting and can be used. The fix, based on vendor
   code and bootloader behavior, is as for time being only
   for MCPM enabled path.
2. Fix thermal boot issue on SMDK5250.
3. Fix invalid clock used for FIMD IOMMU.

----------------------------------------------------------------
Chanho Park (1):
      ARM: EXYNOS: reset Little cores when cpu is up

Joonyoung Shim (1):
      ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420

Yadwinder Singh Brar (1):
      ARM: dts: Fix bootup thermal issue on smdk5250

 arch/arm/boot/dts/exynos5250-smdk5250.dts |  1 +
 arch/arm/boot/dts/exynos5420.dtsi         |  2 +-
 arch/arm/mach-exynos/mcpm-exynos.c        | 27 ++++++++++++++++++++++++++-
 arch/arm/mach-exynos/regs-pmu.h           |  6 ++++++
 4 files changed, 34 insertions(+), 2 deletions(-)

Comments

'Kukjin Kim' Sept. 30, 2015, 6:50 a.m. UTC | #1
On 09/30/15 08:59, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> Below you will find fixes for current release cycle which are not
> present yet in your tree.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-fixes-4.3
> 
> for you to fetch changes up to c7d2ecd9f64c351cb4d551f1f472d0fc09c3cae8:
> 
>   ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420 (2015-09-29 15:39:58 +0900)
> 
> ----------------------------------------------------------------
> Fixes for Exynos (DT and mach code):
> 1. Finally fix booting of all 8 cores on Exynos Octa (Exynos542x): all
>    8 cores are booting and can be used. The fix, based on vendor
>    code and bootloader behavior, is as for time being only
>    for MCPM enabled path.
> 2. Fix thermal boot issue on SMDK5250.
> 3. Fix invalid clock used for FIMD IOMMU.
> 
Pulled, thanks.

Note it will be sent to upstream in a day.

- Kukjin
Krzysztof Kozlowski Oct. 4, 2015, 11:59 p.m. UTC | #2
On 30.09.2015 15:50, Kukjin Kim wrote:
> On 09/30/15 08:59, Krzysztof Kozlowski wrote:
>> Dear Kukjin,
>>
>> Below you will find fixes for current release cycle which are not
>> present yet in your tree.
>>
>> Best regards,
>> Krzysztof
>>
>>
>> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
>>
>>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
>>
>> are available in the git repository at:
>>
>>   https://github.com/krzk/linux.git tags/samsung-fixes-4.3
>>
>> for you to fetch changes up to c7d2ecd9f64c351cb4d551f1f472d0fc09c3cae8:
>>
>>   ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420 (2015-09-29 15:39:58 +0900)
>>
>> ----------------------------------------------------------------
>> Fixes for Exynos (DT and mach code):
>> 1. Finally fix booting of all 8 cores on Exynos Octa (Exynos542x): all
>>    8 cores are booting and can be used. The fix, based on vendor
>>    code and bootloader behavior, is as for time being only
>>    for MCPM enabled path.
>> 2. Fix thermal boot issue on SMDK5250.
>> 3. Fix invalid clock used for FIMD IOMMU.
>>
> Pulled, thanks.
> 
> Note it will be sent to upstream in a day.

A day extended to a week. Please do not hold the fixes but send them. If
they reached Linus tree late and they required any further fix, then we
would have less time for any updates.

The same applies for regular pull request for 4.4. For previous v4.3
release many changes were too late (so they could even slip from 4.3 to
4.4). Can we just avoid such issues and send pull requests earlier?

Best regards,
Krzysztof
'Kukjin Kim' Oct. 5, 2015, 1:36 a.m. UTC | #3
Krzysztof Kozlowski wrote:
> 
> On 30.09.2015 15:50, Kukjin Kim wrote:
> > On 09/30/15 08:59, Krzysztof Kozlowski wrote:
> >> Dear Kukjin,
> >>
> >> Below you will find fixes for current release cycle which are not
> >> present yet in your tree.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >>
> >> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> >>
> >>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> >>
> >> are available in the git repository at:
> >>
> >>   https://github.com/krzk/linux.git tags/samsung-fixes-4.3
> >>
> >> for you to fetch changes up to c7d2ecd9f64c351cb4d551f1f472d0fc09c3cae8:
> >>
> >>   ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420 (2015-09-29 15:39:58 +0900)
> >>
> >> ----------------------------------------------------------------
> >> Fixes for Exynos (DT and mach code):
> >> 1. Finally fix booting of all 8 cores on Exynos Octa (Exynos542x): all
> >>    8 cores are booting and can be used. The fix, based on vendor
> >>    code and bootloader behavior, is as for time being only
> >>    for MCPM enabled path.
> >> 2. Fix thermal boot issue on SMDK5250.
> >> 3. Fix invalid clock used for FIMD IOMMU.
> >>
> > Pulled, thanks.
> >
> > Note it will be sent to upstream in a day.
> 
> A day extended to a week. Please do not hold the fixes but send them. If
> they reached Linus tree late and they required any further fix, then we
> would have less time for any updates.
> 
Sorry for the delay and it's my fault. I'll handle it tonight...

> The same applies for regular pull request for 4.4. For previous v4.3
> release many changes were too late (so they could even slip from 4.3 to
> 4.4). Can we just avoid such issues and send pull requests earlier?
> 
Krzysztof, I sent a pull request lately because of handling of cross-tree but I
don't think so it causes some missing because it was due to cross tree not only
mine. Please don't worry about that I'll handle it.

Anyway thanks for your gentle reminder.

- Kukjin