From: Joe Perches <joe@perches.com>
To: Len Brown <lenb@kernel.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] [27/2many] MAINTAINERS - ACPI THERMAL DRIVER
Date: Mon, 13 Aug 2007 21:36:51 -0700 [thread overview]
Message-ID: <1187066211.32555.23.camel@localhost> (raw)
In-Reply-To: <200708140023.52780.lenb@kernel.org>
On Tue, 2007-08-14 at 00:23 -0400, Len Brown wrote:
> Also, as Konstantin has moved on, might as well list me as maintainer too:
ACPI THERMAL DRIVER
P: Len Brown
M: len.brown@intel.com
L: linux-acpi@vger.kernel.org
W: http://acpi.sourceforge.net/
S: Supported
F: drivers/acpi/*thermal*
prev parent reply other threads:[~2007-08-14 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:22 [PATCH] [27/2many] MAINTAINERS - ACPI THERMAL DRIVER joe
2007-08-14 4:23 ` Len Brown
2007-08-14 4:36 ` Joe Perches [this message]
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=1187066211.32555.23.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).