From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Non-critical fixes for v4.3
Date: Sat, 25 Jul 2015 10:49:54 +0900 [thread overview]
Message-ID: <058101d0c67c$367e0fe0$a37a2fa0$@kernel.org> (raw)
In-Reply-To: <CAJKOXPcEFmOnffViq8X+NxmAB=_wLKj9oLHy28dpYqp4z4QnQQ@mail.gmail.com>
Krzysztof Kozlowski wrote:
>
> 2015-07-24 20:04 GMT+09:00 Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>:
> >
> > Hi,
> >
> > On Friday, July 24, 2015 03:34:55 PM Krzysztof Kozlowski wrote:
> >> Dear Kukjin,
> >>
> >> Previously you did not picked up the fix for cpufreq memory leak.
> >> I am sending it again with respective acks from LKML. Also another
> >> minor improvement in the set.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >>
> >> The following changes since commit 1c4c7159ed2468f3ac4ce5a7f08d79663d381a93:
> >>
> >> Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
> (2015-07-05 16:24:54 -0700)
> >>
> >> are available in the git repository at:
> >>
> >>
> >> https://github.com/krzk/linux.git tags/samsung-fixes-non-critical-v4.3-2
> >>
> >> for you to fetch changes up to 434213f727c12fab8657c8db3d23da4b0463365d:
> >>
> >> video: fbdev: s3c-fb: Constify platform_device_id (2015-07-24 15:17:32 +0900)
> >>
> >> ----------------------------------------------------------------
> >> Improvements for Exynos boards:
> >> 1. Fix memory leak in cpufreq error path.
> >> 2. Constify platform_device_id in video/fbdev/s3c-fb.
> >>
> >> ----------------------------------------------------------------
> >> Krzysztof Kozlowski (1):
> >> video: fbdev: s3c-fb: Constify platform_device_id
> >>
> >> Shailendra Verma (1):
> >> cpufreq: exynos: Fix for memory leak in case SOC name does not match
> >
> > I would suggest merging this fix in v4.2 not v4.3:
> >
> > - it is obvious and touches only error paths
>
> Indeed, good point, thanks for pointing this. Although these are not
> regressions for issues introduced in current release but they are are
> non-intrusive.
>
> Kukjin, do you agree? Can you pull them for second round of v4.2 fixes (not 4.3)
>
Agreed. OK.
> > - (hopefully) in v4.3 the exynos-cpufreq driver will be completely
> > replaced by using cpufreq-dt for Exynos platforms (thus there will be
> > no benefits of having this fix in v4.3 but there will be potential
> > risk of merge conflicts due to exynos-cpufreq driver removal)
> >
>
> We'll see... The Exynos 4x12 requires OPP patches. Are these ready for 4.3?
>
I think, if any conflicts based on fixes during -rc, can be handled by
maintainer.
Thanks,
Kukjin
prev parent reply other threads:[~2015-07-25 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 6:34 [GIT PULL] Non-critical fixes for v4.3 Krzysztof Kozlowski
2015-07-24 11:04 ` Bartlomiej Zolnierkiewicz
2015-07-24 11:49 ` Krzysztof Kozlowski
2015-07-25 1:49 ` Kukjin Kim [this message]
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='058101d0c67c$367e0fe0$a37a2fa0$@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).