From: Len Brown <lenb@kernel.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-acpi@vger.kernel.org, calvinmc@gmail.com,
acpi4asus-user@lists.sourceforge.net
Subject: Re: [patch 19/19] asus_acpi: Add support for Asus Z81SP
Date: Fri, 5 Jan 2007 02:06:22 -0500 [thread overview]
Message-ID: <200701050206.22992.lenb@kernel.org> (raw)
In-Reply-To: <20061222201511.e9f6ef16.akpm@osdl.org>
On Friday 22 December 2006 23:15, Andrew Morton wrote:
> On Fri, 22 Dec 2006 21:13:23 -0500
> Len Brown <lenb@kernel.org> wrote:
>
> > NAK
> >
> > The proper way to update the asus_acpi driver
> > is through its (new) maintainer and mailing list on acpi4asus-user@lists.sourceforge.net
> > which will forward the patches through the acpi tree when tested.
> >
>
> So why the NAK? The patch is good, isn't it?
Okay, call it lack of an ACK:-)
When it comes from the asus_acpi maintainer having passed the muster of
the acpi4asus-user list I'll be delighted to apply it.
cheers,
-Len
prev parent reply other threads:[~2007-01-05 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 20:56 [patch 19/19] asus_acpi: Add support for Asus Z81SP akpm
2006-12-23 2:13 ` Len Brown
2006-12-23 4:15 ` Andrew Morton
2007-01-05 7:06 ` Len Brown [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=200701050206.22992.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=calvinmc@gmail.com \
--cc=linux-acpi@vger.kernel.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