From: Andi Kleen <andi@firstfloor.org>
To: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: lenb@kernel.org, torvalds@osdl.org, akpm@osdl.org, acpi@linux.intel.com
Subject: Temporary ACPI maintainer for this summer
Date: Mon, 30 Jun 2008 15:43:33 +0200 [thread overview]
Message-ID: <871w2fujga.fsf@basil.nowhere.org> (raw)
Len Brown is on sabbatical from Intel this summer. While he's away
I'm serving as the temporary ACPI maintainer. Please send all ACPI
mails and patches you would normally send to Len to me, ideally cc
linux-acpi@vger.kernel.org.
As usual please put all ACPI bug reports into http://bugzilla.kernel.org.
First (in case he still reads that) I would like to thank Len (and all
the other ACPI hackers of course) for all the great work done on the ACPI
code in the last years, turning it from a problem child to a quite
respectable kernel subsystem.
I'm not as deep in all things ACPI as Len is, so I'll often rely on
the various other ACPI hackers for specific issues.
My main goal will be to merge patches from the usual contributors and
try to keep the ACPI bugs and regressions under control. I don't plan
many new features, but features already in progress will be processed
as they are ready.
I'm also not full time working on ACPI, but also active in other areas.
This means I will not write that many ACPI patches myself
or do extensive testing on my own, but mostly focus on review and merging
and bug triage.
The git tree setup for the merges will be announced later. I won't
directly use Len's tree.
I'll take over all patches Len has already queued, so no need to
resubmit them. But if he doesn't have something acknowledged already
you want to be included, please retransmit it to me.
The .27 merge will be primarily patches Len has already queued
in his release tree.
-Andi
next reply other threads:[~2008-06-30 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 13:43 Andi Kleen [this message]
2008-06-30 16:50 ` Temporary ACPI maintainer for this summer Henrique de Moraes Holschuh
2008-06-30 17:23 ` Andi Kleen
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=871w2fujga.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=acpi@linux.intel.com \
--cc=akpm@osdl.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).