From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung fixes for v4.3
Date: Mon, 05 Oct 2015 10:36:28 +0900 [thread overview]
Message-ID: <124301d0ff0e$4162bf80$c4283e80$@kernel.org> (raw)
In-Reply-To: <5611BD49.5030806@samsung.com>
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
next prev parent reply other threads:[~2015-10-05 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 23:59 [GIT PULL] Samsung fixes for v4.3 Krzysztof Kozlowski
2015-09-30 6:50 ` Kukjin Kim
2015-10-04 23:59 ` Krzysztof Kozlowski
2015-10-05 1:36 ` Kukjin Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-05 22:57 Kukjin Kim
2015-10-06 12:27 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='124301d0ff0e$4162bf80$c4283e80$@kernel.org' \
--to=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).