From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: Kukjin Kim <kgene@kernel.org>,
'Bartlomiej Zolnierkiewicz' <b.zolnierkie@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
'Marek Szyprowski' <m.szyprowski@samsung.com>,
'Tomasz Figa' <tomasz.figa@gmail.com>,
Mark Rutland <Mark.Rutland@arm.com>,
'Thomas Abraham' <ta.omasab@gmail.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>
Subject: Re: [PATCH v3] ARM: dts: add CPU nodes for Exynos4 SoCs
Date: Thu, 16 Oct 2014 11:48:59 +0100 [thread overview]
Message-ID: <20141016104859.GA29308@red-moon> (raw)
In-Reply-To: <5423D19B.1040203@samsung.com>
On Thu, Sep 25, 2014 at 09:26:03AM +0100, Kukjin Kim wrote:
> On 09/25/14 17:17, Lorenzo Pieralisi wrote:
> > [CC'ed Daniel to make him aware this patch goes through your tree]
> >
> Thanks and just note the branch which is including this change actually
> v4 is just rebased not v3 will be sent out to arm-soc last tonight or
> tomorrow.
What's the plan for patch ? I do not see it upstream and would like
to rebase the Exynos CPUidle changes on top of it.
Thanks,
Lorenzo
WARNING: multiple messages have this Message-ID (diff)
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: dts: add CPU nodes for Exynos4 SoCs
Date: Thu, 16 Oct 2014 11:48:59 +0100 [thread overview]
Message-ID: <20141016104859.GA29308@red-moon> (raw)
In-Reply-To: <5423D19B.1040203@samsung.com>
On Thu, Sep 25, 2014 at 09:26:03AM +0100, Kukjin Kim wrote:
> On 09/25/14 17:17, Lorenzo Pieralisi wrote:
> > [CC'ed Daniel to make him aware this patch goes through your tree]
> >
> Thanks and just note the branch which is including this change actually
> v4 is just rebased not v3 will be sent out to arm-soc last tonight or
> tomorrow.
What's the plan for patch ? I do not see it upstream and would like
to rebase the Exynos CPUidle changes on top of it.
Thanks,
Lorenzo
next prev parent reply other threads:[~2014-10-16 10:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 13:09 [PATCH v3] ARM: dts: add CPU nodes for Exynos4 SoCs Bartlomiej Zolnierkiewicz
2014-09-24 13:09 ` Bartlomiej Zolnierkiewicz
2014-09-25 5:56 ` Kukjin Kim
2014-09-25 5:56 ` Kukjin Kim
2014-09-25 8:17 ` Lorenzo Pieralisi
2014-09-25 8:17 ` Lorenzo Pieralisi
2014-09-25 8:26 ` Kukjin Kim
2014-09-25 8:26 ` Kukjin Kim
2014-09-25 8:28 ` Tomasz Figa
2014-09-25 8:28 ` Tomasz Figa
2014-09-25 8:44 ` Kukjin Kim
2014-09-25 8:44 ` Kukjin Kim
2014-09-25 8:57 ` Tomasz Figa
2014-09-25 8:57 ` Tomasz Figa
2014-10-16 10:48 ` Lorenzo Pieralisi [this message]
2014-10-16 10:48 ` Lorenzo Pieralisi
2014-09-25 9:02 ` Daniel Lezcano
2014-09-25 9:02 ` Daniel Lezcano
2014-09-25 9:36 ` Lorenzo Pieralisi
2014-09-25 9:36 ` Lorenzo Pieralisi
2014-09-25 12:24 ` Daniel Lezcano
2014-09-25 12:24 ` Daniel Lezcano
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=20141016104859.GA29308@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.lezcano@linaro.org \
--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=m.szyprowski@samsung.com \
--cc=ta.omasab@gmail.com \
--cc=tomasz.figa@gmail.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 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.