From: Jason Cooper <jason@lakedaemon.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@linaro.org>,
arm@kernel.org, Andrew Lunn <andrew@lunn.ch>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org
Subject: Re: [GIT PULL] ARM: mvebu: SoC changes for v3.17 (round 3)
Date: Wed, 23 Jul 2014 19:41:30 -0400 [thread overview]
Message-ID: <20140723234130.GM23220@titan.lakedaemon.net> (raw)
In-Reply-To: <201407232231.41787.arnd@arndb.de>
On Wed, Jul 23, 2014 at 10:31:41PM +0200, Arnd Bergmann wrote:
> On Tuesday 22 July 2014, Jason Cooper wrote:
> > All,
> >
> > Here's the cpufreq changes I mentioned over the weekend. It's been in
> > -next for a while. Once I get the new version of cpuidle from ThomasP,
> > I'll push that as quickly as possible.
>
> Just for my information, is this coordinated with the cpufreq maintainers?
> I remember being asked to ensure all cpufreq/cpuidle stuff has an Ack
> from them, even stuff that doesn't touch drivers/cpufreq at all.
Good to know.
> The contents look good to me. I can merge them if there are no objections
> from Viresh, feel free to send the next batch already without waiting
> for me to pull.
We've been coordinating with Viresh. He has an unsettled issue on his
side he hopes to have resolved soon. Worst case scenario, he doesn't
get the change in for v3.17, we'll have to do a minor DT fix on top of
-rc1.
> > As usual (do I need to type this each time any more? :) ), this is an
> > incremental pull request from tags/mvebu-soc-3.17-2 up to
> > tags/mvebu-soc-3.17-3 on the mvebu/soc branch.
>
> It certainly helps me to have this information, but you can write it
> more briefly, e.g. "based on tags/mvebu-soc-3.17-2".
Ahhhh.... Much more succinct. Thank you. On a side note, I wonder
what it would take to get 'git request-pull' smart enough to add that
information when handed a tag?
> > The following changes since commit ba364fc752daeded072a5ef31e43b84cb1f9e5fd:
> >
> > ARM: Kirkwood: Remove mach-kirkwood (2014-07-13 22:13:39 +0000)
eg:
ARM: Kirkwood: Remove mach-kirkwood (tags/mvebu-soc-3.17-2)
> >
> > are available in the git repository at:
> >
> > git://git.infradead.org/linux-mvebu.git tags/mvebu-soc-3.17-3
> >
> > for you to fetch changes up to ba3ec5780bba27819bbc4f669e6c77418a00f14b:
> >
> > Merge branch 'mvebu/soc-cpufreq' into mvebu/soc (2014-07-22 20:46:48 +0000)
> >
> > ----------------------------------------------------------------
Is the date of the base commit useful in any way in the pull request?
thx,
Jason.
next prev parent reply other threads:[~2014-07-23 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140722205706.GA23220@titan.lakedaemon.net>
2014-07-23 20:31 ` [GIT PULL] ARM: mvebu: SoC changes for v3.17 (round 3) Arnd Bergmann
2014-07-23 23:41 ` Jason Cooper [this message]
2014-07-23 23:45 ` Olof Johansson
2014-07-24 0:08 ` Jason Cooper
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=20140723234130.GM23220@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=gregory.clement@free-electrons.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=sebastian.hesselbarth@googlemail.com \
--cc=viresh.kumar@linaro.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