linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "pankaj.dubey" <pankaj.dubey@samsung.com>
To: Kukjin Kim <kgene@kernel.org>, Pavel Fedin <p.fedin@samsung.com>
Cc: "'Krzysztof Kozlowski'" <k.kozlowski@samsung.com>,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kgene.kim@samsung.com,
	thomas.ab@samsung.com, andi.shyti@samsung.com
Subject: Re: [PATCH v5 0/8] Add support for Exynos SROM Controller driver
Date: Tue, 17 Nov 2015 10:29:10 +0530	[thread overview]
Message-ID: <564AB41E.4090107@samsung.com> (raw)
In-Reply-To: <562A7A03.8040704@kernel.org>

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) board. Unless Kukjin picks
>>> it also, I plan to take it for v4.5.
>>
>>  Tested on SMDK5410. By the way, what is current status? If this is final revision, can i post my Ethernet support patchset on top
>> of it?
>>
>>  Tested-by: Pavel Fedin <p.fedin@samsung.com>
>>
> Applied, this whole series.
> 

I just pulled your tree, and I can't find these SROM patches in for-next
(earlier they were present). Also I can see samsung for-next is pointing
to linus/master branch. As this series not landed in linus tree due last
moment changes, So do I need to rebase SROM patches on top of latest
for-next, and send it once again?

Thanks,
Pankaj Dubey

> Thanks,
> Kukjin
> 

      parent reply	other threads:[~2015-11-17  4:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  9:15 [PATCH v5 0/8] Add support for Exynos SROM Controller driver Pankaj Dubey
2015-10-20  9:15 ` [PATCH v5 1/8] ARM: EXYNOS: remove unused static mapping of CMU for exynos5 Pankaj Dubey
2015-10-20  9:15 ` [PATCH v5 2/8] ARM: EXYNOS: code cleanup in map.h Pankaj Dubey
2015-10-20  9:15 ` [PATCH v5 3/8] Documentation: dt-bindings: add exynos-srom binding information Pankaj Dubey
2015-10-20  9:15 ` [PATCH v5 4/8] ARM: dts: add SROM device node for exynos4 Pankaj Dubey
2015-10-20  9:15 ` [PATCH v5 5/8] ARM: dts: add SROM device node for exynos5 Pankaj Dubey
2015-10-20  9:15 ` [PATCH v5 6/8] drivers: soc: add support for exynos SROM driver Pankaj Dubey
2015-10-20 11:14   ` Andi Shyti
2015-10-20 12:37   ` Krzysztof Kozlowski
2015-10-20  9:15 ` [PATCH v5 7/8] MAINTAINERS: add maintainers entry for drivers/soc/samsung Pankaj Dubey
2015-10-20  9:15 ` [PATCH v5 8/8] ARM: EXYNOS: Remove SROM related register settings from mach-exynos Pankaj Dubey
2015-10-23 18:34   ` Kukjin Kim
2015-10-21  0:34 ` [PATCH v5 0/8] Add support for Exynos SROM Controller driver Krzysztof Kozlowski
2015-10-23  9:49   ` Pavel Fedin
2015-10-23 18:18     ` Kukjin Kim
2015-10-26  6:45       ` Pavel Fedin
2015-10-27  2:15         ` Kukjin Kim
2015-10-27  7:17           ` Pavel Fedin
2015-11-17  4:59       ` pankaj.dubey [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=564AB41E.4090107@samsung.com \
    --to=pankaj.dubey@samsung.com \
    --cc=andi.shyti@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=p.fedin@samsung.com \
    --cc=thomas.ab@samsung.com \
    /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).