From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Jones <davej@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
cpufreq@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add myself as the cpufreq maintainer
Date: Sun, 13 May 2012 15:12:36 +0200 [thread overview]
Message-ID: <201205131512.36250.rjw@sisk.pl> (raw)
In-Reply-To: <20120513101931.39617e4909fcc10d6739bc75@canb.auug.org.au>
Hi Stephen,
On Sunday, May 13, 2012, Stephen Rothwell wrote:
> Hi Rafael, Dave,
>
> On Fri, 11 May 2012 21:35:45 +0200 "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > Since cpufreq has no official maintainer at the moment, I'm willing
> > to maintain it along some other power management core code I've been
> > maintaining already.
>
> I have cpufreq-current and cpufreq trees in linux-next (both currently
> empty and with Dave as contact). What should I do with them?
>
> cpufreq-current git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git#fixes
> cpufreq git://git.kernel.org/pub/scm/linux/kernel/git/davej/cpufreq.git#next
I will push future cpufreq updates through the linux-pm tree.
Thanks,
Rafael
next prev parent reply other threads:[~2012-05-13 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 16:04 CPU frequency drivers MAINTAINERS update Dave Jones
2012-05-04 16:50 ` Joe Perches
2012-05-05 19:10 ` Rafael J. Wysocki
2012-05-11 19:16 ` Rafael J. Wysocki
2012-05-11 19:24 ` Dave Jones
2012-05-11 19:34 ` Rafael J. Wysocki
2012-05-11 19:35 ` [PATCH] MAINTAINERS: Add myself as the cpufreq maintainer Rafael J. Wysocki
2012-05-13 0:19 ` Stephen Rothwell
2012-05-13 13:12 ` Rafael J. Wysocki [this message]
2012-05-13 14:03 ` Stephen Rothwell
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=201205131512.36250.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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
all inboxes | Powered by JetHome®