Hi Krzysztof,
On Thursday 17 December 2015 10:44 AM, Krzysztof Kozlowski wrote:
> On 12.12.2015 16:43, Pankaj Dubey wrote:
>> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
>>
>> Series v5 got merged in kgene/for-next but due to last moment change before
>> pull
>> these
Hi Krzysztof,
On Thursday 17 December 2015 10:44 AM, Krzysztof Kozlowski wrote:
> On 12.12.2015 16:43, Pankaj Dubey wrote:
>> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
>>
>> Series v5 got merged in kgene/for-next but due to last moment change before
>> pull
>> these
On 12.12.2015 16:43, Pankaj Dubey wrote:
> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
>
> Series v5 got merged in kgene/for-next but due to last moment change before
> pull
> these patches were not accepted during 4.3 merge window.After that
> kgene/for-next
> got
On 12.12.2015 16:43, Pankaj Dubey wrote:
> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
>
> Series v5 got merged in kgene/for-next but due to last moment change before
> pull
> these patches were not accepted during 4.3 merge window.After that
> kgene/for-next
> got
Hello!
> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
>
> Series v5 got merged in kgene/for-next but due to last moment change before
> pull
> these patches were not accepted during 4.3 merge window.After that
> kgene/for-next
> got rebased over 4.4-rc1 these patches
Hello!
> THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
>
> Series v5 got merged in kgene/for-next but due to last moment change before
> pull
> these patches were not accepted during 4.3 merge window.After that
> kgene/for-next
> got rebased over 4.4-rc1 these patches
THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
Series v5 got merged in kgene/for-next but due to last moment change before pull
these patches were not accepted during 4.3 merge window.After that
kgene/for-next
got rebased over 4.4-rc1 these patches got dropped into another
THIS IS A RESEND OF ONCE MERGED INTO kgene/for-next AND LOST PATCHES
Series v5 got merged in kgene/for-next but due to last moment change before pull
these patches were not accepted during 4.3 merge window.After that
kgene/for-next
got rebased over 4.4-rc1 these patches got dropped into another
Hi Kukjin
On Friday 23 October 2015 11:48 PM, Kukjin Kim wrote:
> On 10/23/15 18:49, Pavel Fedin wrote:
>> Hello!
>>
This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for
boot
and S2R functionality.
>>>
>>> Entire patchset tested on Trats2 (Exynos4412)
Hi Kukjin
On Friday 23 October 2015 11:48 PM, Kukjin Kim wrote:
> On 10/23/15 18:49, Pavel Fedin wrote:
>> Hello!
>>
This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for
boot
and S2R functionality.
>>>
>>> Entire patchset tested on Trats2 (Exynos4412)
Hello!
> You may need to fetch again?
> Anyway the branch is v4.4-next/driver-samsung or tags/samsung-driver...
> Or just for-next should be fine I think.
Thank you very much, already found it, and even posted my series, you should
have already seen it.
Kind regards,
Pavel Fedin
Expert
Hello!
> You may need to fetch again?
> Anyway the branch is v4.4-next/driver-samsung or tags/samsung-driver...
> Or just for-next should be fine I think.
Thank you very much, already found it, and even posted my series, you should
have already seen it.
Kind regards,
Pavel Fedin
Expert
On 10/26/15 15:45, Pavel Fedin wrote:
> Hello!
>
Hi,
>> Applied, this whole series.
>
> Where can i find the recent code to base my series on? I looked at
> linux-samsung.git but was unable to find it there.
>
You may need to fetch again?
Anyway the branch is v4.4-next/driver-samsung or
Hello!
> Applied, this whole series.
Where can i find the recent code to base my series on? I looked at
linux-samsung.git but was unable to find it there.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line
Hello!
> Applied, this whole series.
Where can i find the recent code to base my series on? I looked at
linux-samsung.git but was unable to find it there.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
To unsubscribe from this list: send the line
On 10/26/15 15:45, Pavel Fedin wrote:
> Hello!
>
Hi,
>> Applied, this whole series.
>
> Where can i find the recent code to base my series on? I looked at
> linux-samsung.git but was unable to find it there.
>
You may need to fetch again?
Anyway the branch is v4.4-next/driver-samsung or
On 10/23/15 18:49, Pavel Fedin wrote:
> Hello!
>
>>> This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for
>>> boot
>>> and S2R functionality.
>>>
>>
>> Entire patchset tested on Trats2 (Exynos4412) board. Unless Kukjin picks
>> it also, I plan to take it for v4.5.
>
>
Hello!
> > This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for
> > boot
> > and S2R functionality.
> >
>
> Entire patchset tested on Trats2 (Exynos4412) board. Unless Kukjin picks
> it also, I plan to take it for v4.5.
Tested on SMDK5410. By the way, what is current
On 10/23/15 18:49, Pavel Fedin wrote:
> Hello!
>
>>> This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for
>>> boot
>>> and S2R functionality.
>>>
>>
>> Entire patchset tested on Trats2 (Exynos4412) board. Unless Kukjin picks
>> it also, I plan to take it for v4.5.
>
>
Hello!
> > This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for
> > boot
> > and S2R functionality.
> >
>
> Entire patchset tested on Trats2 (Exynos4412) board. Unless Kukjin picks
> it also, I plan to take it for v4.5.
Tested on SMDK5410. By the way, what is current
On 20.10.2015 18:15, Pankaj Dubey wrote:
> This patch set adds support for Exynos SROM controller DT based driver.
> Currently SROM register sets are used only during S2R, so driver
> basically added for taking care of S2R. It will help us in removing
> static mapping from exynos.c and other extra
This patch set adds support for Exynos SROM controller DT based driver.
Currently SROM register sets are used only during S2R, so driver
basically added for taking care of S2R. It will help us in removing
static mapping from exynos.c and other extra code handline during S2R.
This patch set also
This patch set adds support for Exynos SROM controller DT based driver.
Currently SROM register sets are used only during S2R, so driver
basically added for taking care of S2R. It will help us in removing
static mapping from exynos.c and other extra code handline during S2R.
This patch set also
On 20.10.2015 18:15, Pankaj Dubey wrote:
> This patch set adds support for Exynos SROM controller DT based driver.
> Currently SROM register sets are used only during S2R, so driver
> basically added for taking care of S2R. It will help us in removing
> static mapping from exynos.c and other extra
24 matches
Mail list logo
