From: davej@redhat.com (Dave Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: CPUFREQ maintainence.
Date: Mon, 30 Apr 2012 10:06:45 -0400 [thread overview]
Message-ID: <20120430140645.GB12583@redhat.com> (raw)
This last few releases I've been more of a hindrance than help to getting
some of the patches merged upstream, so due to my lack of time, I'm considering
removing myself as maintainer, and having patches routed as such instead...
ARM -> Russell/relevant ARM subtree maintainers
x86 driver patches -> x86 at vger.kernel.org
(All the other archs currently supported already go through the arch trees mips/sparc etc)
The core doesn't see a huge amount of change these days, I figure patches for
that can just go to lkml & Linus/Andrew like any other subsystem.
comments?
Dave
next reply other threads:[~2012-04-30 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 14:06 Dave Jones [this message]
2012-05-08 6:16 ` CPUFREQ maintainence Kukjin Kim
2012-05-08 16:56 ` 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=20120430140645.GB12583@redhat.com \
--to=davej@redhat.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;
as well as URLs for NNTP newsgroup(s).