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
| ||
|
Message-id: <5611BD49.5030806@samsung.com> Date: Mon, 05 Oct 2015 08:59:05 +0900 From: Krzysztof Kozlowski <k.kozlowski@...sung.com> To: Kukjin Kim <kgene@...nel.org> Cc: linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org, Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>, Kevin Hilman <khilman@...nel.org> Subject: Re: [GIT PULL] Samsung fixes for v4.3 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 -- 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