All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Kukjin Kim <kgene@kernel.org>
Cc: '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>
Subject: Re: [PATCH v3] ARM: dts: add CPU nodes for Exynos4 SoCs
Date: Thu, 25 Sep 2014 11:02:05 +0200	[thread overview]
Message-ID: <5423DA0D.9030100@linaro.org> (raw)
In-Reply-To: <20140925081704.GA20841@e102568-lin.cambridge.arm.com>

On 09/25/2014 10:17 AM, Lorenzo Pieralisi wrote:
> [CC'ed Daniel to make him aware this patch goes through your tree]

Thanks for the head up. I was about to send the PR to Rafael.

[ ... ]

> That's great, now my Exynos CPUidle DT patch should be rebased on top
> of this patch so that thanks to the testing carried out by Bart it can be
> merged too.

Ok, I am getting confused. How can I rebase the latest patch of your 
series with a patch no yet available in my tree ?

I propose just to drop the last patch and wait for the next merge to 
reintegrate it into the cpuidle tree. Does it make sense ?

Thanks
   -- Daniel


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: dts: add CPU nodes for Exynos4 SoCs
Date: Thu, 25 Sep 2014 11:02:05 +0200	[thread overview]
Message-ID: <5423DA0D.9030100@linaro.org> (raw)
In-Reply-To: <20140925081704.GA20841@e102568-lin.cambridge.arm.com>

On 09/25/2014 10:17 AM, Lorenzo Pieralisi wrote:
> [CC'ed Daniel to make him aware this patch goes through your tree]

Thanks for the head up. I was about to send the PR to Rafael.

[ ... ]

> That's great, now my Exynos CPUidle DT patch should be rebased on top
> of this patch so that thanks to the testing carried out by Bart it can be
> merged too.

Ok, I am getting confused. How can I rebase the latest patch of your 
series with a patch no yet available in my tree ?

I propose just to drop the last patch and wait for the next merge to 
reintegrate it into the cpuidle tree. Does it make sense ?

Thanks
   -- Daniel


-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  parent reply	other threads:[~2014-09-25  9:02 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
2014-10-16 10:48         ` Lorenzo Pieralisi
2014-09-25  9:02     ` Daniel Lezcano [this message]
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=5423DA0D.9030100@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=Mark.Rutland@arm.com \
    --cc=b.zolnierkie@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=lorenzo.pieralisi@arm.com \
    --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.