From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: MAINTAINERS: Add git tree path for ARM specific updates
Date: Wed, 29 May 2013 03:47:02 -0700 [thread overview]
Message-ID: <1369824422.22004.101.camel@joe-AO722> (raw)
In-Reply-To: <aab5b5dc92b960e81e8fd1975eba81234a4ecac8.1369817795.git.viresh.kumar@linaro.org>
On Wed, 2013-05-29 at 16:10 +0530, Viresh Kumar wrote:
> ARM specific patches would be
> Applied by me now. Rafael will pull in these changes from time to time (at
> rc's).
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -2216,6 +2216,7 @@ L: cpufreq at vger.kernel.org
[]
> T: git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> +T: git://git.linaro.org/people/vireshk/linux.git (For ARM Updates)
please prefix these with git
T: git git://git.etc...
Every other T: git entry does.
next prev parent reply other threads:[~2013-05-29 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 10:40 [PATCH] cpufreq: MAINTAINERS: Add git tree path for ARM specific updates Viresh Kumar
2013-05-29 10:47 ` Joe Perches [this message]
2013-05-29 10:54 ` Viresh Kumar
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=1369824422.22004.101.camel@joe-AO722 \
--to=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.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