From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kevin Hilman <khilman@ti.com>, Rob Lee <rob.lee@linaro.org>,
Lists Linaro-dev <linaro-dev@lists.linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
linux-acpi@vger.kernel.org, linux-next@vger.kernel.org,
Colin Cross <ccross@android.com>,
linux-pm@lists.linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>
Subject: Re: linux-next : cpuidle - could you add my tree please
Date: Tue, 03 Jul 2012 15:25:39 +0200 [thread overview]
Message-ID: <4FF2F2D3.4090200@linaro.org> (raw)
In-Reply-To: <20120703231948.33cca18e3cc3d6e497ab022d@canb.auug.org.au>
On 07/03/2012 03:19 PM, Stephen Rothwell wrote:
> Hi Daniel,
>
> On Tue, 03 Jul 2012 14:56:58 +0200 Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>>
>>> So do you have a branch in the cpuidle-next.git tree that isn't going to
>>> be rebased?
>>
>> No. I am following Linus tree and adding the patches on top of it.
>
> Please don't rebase your tree more than necessary - it just makes thing
> hard for anyone using your tree as a base for further development and
> throws away any testing you may have done.
Ok, let me sync with Len and Rafael about the best way to do that.
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
next prev parent reply other threads:[~2012-07-03 13:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 8:40 cpuidle future and improvements Daniel Lezcano
2012-06-18 11:54 ` Deepthi Dharwar
2012-06-18 12:35 ` Daniel Lezcano
2012-06-18 12:53 ` Peter De Schrijver
2012-06-18 12:55 ` Daniel Lezcano
2012-06-18 13:06 ` Jean Pihet
2012-06-18 13:26 ` Daniel Lezcano
2012-06-18 13:30 ` [linux-pm] " a0393909
2012-06-25 12:58 ` Shilimkar, Santosh
2012-06-25 13:10 ` Daniel Lezcano
2012-06-25 13:17 ` Shilimkar, Santosh
2012-06-25 13:27 ` linux-next : cpuidle - could you add my tree please Daniel Lezcano
2012-06-25 22:53 ` Stephen Rothwell
2012-07-02 9:09 ` Linus Walleij
2012-07-02 12:51 ` Daniel Lezcano
2012-07-02 19:49 ` Rafael J. Wysocki
2012-07-02 22:14 ` Daniel Lezcano
2012-07-03 8:59 ` Rafael J. Wysocki
2012-07-03 12:56 ` Daniel Lezcano
2012-07-03 13:19 ` Stephen Rothwell
2012-07-03 13:25 ` Daniel Lezcano [this message]
2012-07-03 16:54 ` Rafael J. Wysocki
2012-07-05 13:33 ` Daniel Lezcano
2012-07-03 19:20 ` Linus Walleij
2012-07-03 19:33 ` Rafael J. Wysocki
2012-07-02 20:04 ` Rafael J. Wysocki
2012-06-18 18:15 ` cpuidle future and improvements Colin Cross
2012-06-18 19:00 ` Daniel Lezcano
2012-06-25 12:54 ` Daniel Lezcano
2012-07-11 14:00 ` [linux-pm] " Kevin Hilman
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=4FF2F2D3.4090200@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=amit.kucheria@linaro.org \
--cc=ccross@android.com \
--cc=khilman@ti.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pdeschrijver@nvidia.com \
--cc=rob.lee@linaro.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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).