All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Kukjin Kim <kgene@kernel.org>,
	arm@kernel.org, 'Arnd Bergmann' <arnd@arndb.de>,
	'Olof Johansson' <olof@lixom.net>,
	'Kevin Hilman' <khilman@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/5] Samsung non-critical-fixes for v4.3
Date: Tue, 04 Aug 2015 16:57:02 +0900	[thread overview]
Message-ID: <55C0704E.7020907@samsung.com> (raw)
In-Reply-To: <052201d0ce8a$aba37790$02ea66b0$@kernel.org>

On 04.08.2015 16:53, Kukjin Kim wrote:
> Krzysztof Kozlowski wrote:
>>
>> On 04.08.2015 16:28, Kukjin Kim wrote:
>>> Hi Arnd, Olof, Kevin,
>>>
>>> Here is Samsung non-critical-fixes for v4.3.
>>> Please pull.
>>>
>>> Thanks,
>>> Kukjin
>>>
>>> The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
>>>
>>>   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
>>>
>>> are available in the git repository at:
>>>
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
>>> tags/samsung-non-critical-1
>>>
>>> for you to fetch changes up to 2cc6b813579415c4f627b08a043079bdc5b87a33:
>>>
>>>   ARM: EXYNOS: Use IOMEM_ERR_PTR when function returns iomem (2015-07-21
>>> 13:19:06 +0900)
>>>
>>> ----------------------------------------------------------------
>>> Samsung non-critical fixes for v4.3
>>>
>>> - fix sparse warning for returning iomem
>>> - fix clock-frequency of display timing0 for exynos3250-rinato
>>
> Hi,
> 
>> One more set, which we agreed for pushing to v4.2, is missing:
>> 1. cpufreq: exynos: Fix for memory leak in case SOC name does not match
> 
> As you can see in ml, I've sent it to Rafael because it would be handled in
> cpufreq tree not samsung tree/arm-soc tree.
> 
>> 2. video: fbdev: s3c-fb: Constify platform_device_id (this can actually
> 
> Same as above, this would be handled in fb tree? Can you please send it?

This was on LKML for 3 months (including a resend). As this is S3C frame
buffer I think this can go via samsung-soc tree, since fb guys did not
picked it.

On list of patches few more are also missing:
1. cpufreq: exynos: remove Exynos5250 specific cpufreq driver support
2. clk: samsung: exynos5250: add cpu clock configuration data and
instantiate cpu clock
3. defconfig changes (separate pull request?)

Best regards,
Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/5] Samsung non-critical-fixes for v4.3
Date: Tue, 04 Aug 2015 16:57:02 +0900	[thread overview]
Message-ID: <55C0704E.7020907@samsung.com> (raw)
In-Reply-To: <052201d0ce8a$aba37790$02ea66b0$@kernel.org>

On 04.08.2015 16:53, Kukjin Kim wrote:
> Krzysztof Kozlowski wrote:
>>
>> On 04.08.2015 16:28, Kukjin Kim wrote:
>>> Hi Arnd, Olof, Kevin,
>>>
>>> Here is Samsung non-critical-fixes for v4.3.
>>> Please pull.
>>>
>>> Thanks,
>>> Kukjin
>>>
>>> The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
>>>
>>>   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
>>>
>>> are available in the git repository at:
>>>
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
>>> tags/samsung-non-critical-1
>>>
>>> for you to fetch changes up to 2cc6b813579415c4f627b08a043079bdc5b87a33:
>>>
>>>   ARM: EXYNOS: Use IOMEM_ERR_PTR when function returns iomem (2015-07-21
>>> 13:19:06 +0900)
>>>
>>> ----------------------------------------------------------------
>>> Samsung non-critical fixes for v4.3
>>>
>>> - fix sparse warning for returning iomem
>>> - fix clock-frequency of display timing0 for exynos3250-rinato
>>
> Hi,
> 
>> One more set, which we agreed for pushing to v4.2, is missing:
>> 1. cpufreq: exynos: Fix for memory leak in case SOC name does not match
> 
> As you can see in ml, I've sent it to Rafael because it would be handled in
> cpufreq tree not samsung tree/arm-soc tree.
> 
>> 2. video: fbdev: s3c-fb: Constify platform_device_id (this can actually
> 
> Same as above, this would be handled in fb tree? Can you please send it?

This was on LKML for 3 months (including a resend). As this is S3C frame
buffer I think this can go via samsung-soc tree, since fb guys did not
picked it.

On list of patches few more are also missing:
1. cpufreq: exynos: remove Exynos5250 specific cpufreq driver support
2. clk: samsung: exynos5250: add cpu clock configuration data and
instantiate cpu clock
3. defconfig changes (separate pull request?)

Best regards,
Krzysztof

  reply	other threads:[~2015-08-04  7:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  7:28 [GIT PULL 1/5] Samsung non-critical-fixes for v4.3 Kukjin Kim
2015-08-04  7:28 ` Kukjin Kim
2015-08-04  7:39 ` Krzysztof Kozlowski
2015-08-04  7:39   ` Krzysztof Kozlowski
2015-08-04  7:53   ` Kukjin Kim
2015-08-04  7:53     ` Kukjin Kim
2015-08-04  7:57     ` Krzysztof Kozlowski [this message]
2015-08-04  7:57       ` Krzysztof Kozlowski
2015-08-04  8:11       ` Kukjin Kim
2015-08-04  8:11         ` Kukjin Kim
2015-08-10  0:41 ` Kukjin Kim
2015-08-10  0:41   ` Kukjin Kim
2015-08-11 12:39 ` Olof Johansson
2015-08-11 12:39   ` Olof Johansson

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=55C0704E.7020907@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=kgene@kernel.org \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.