From: Len Brown <lenb@kernel.org>
To: Thomas Renninger <trenn@suse.de>
Cc: Zhang Rui <rui.zhang@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI: support customizing ACPI control methods at runtime
Date: Fri, 11 Dec 2009 01:51:10 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912110150310.6502@localhost.localdomain> (raw)
In-Reply-To: <200912021134.58846.trenn@suse.de>
On Wed, 2 Dec 2009, Thomas Renninger wrote:
> On Wednesday 02 December 2009 06:31:00 Zhang Rui wrote:
> >
> > Introduce a new debugfs I/F (/sys/kernel/debug/acpi/custom_method) for ACPI,
> > which can be used to customize the ACPI control methods at runtime.
> Still no kernel tainting on a successful override?
> On purpose or unintended?
unintended.
Rui, please send a follow-on patch to taint,
just like when we override the DSDT.
thanks,
-Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-12-11 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 5:31 [PATCH] ACPI: support customizing ACPI control methods at runtime Zhang Rui
2009-12-02 10:34 ` Thomas Renninger
2009-12-11 6:51 ` Len Brown [this message]
2009-12-11 7:25 ` Zhang, Rui
2009-12-11 9:54 ` Thomas Renninger
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=alpine.LFD.2.00.0912110150310.6502@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=trenn@suse.de \
/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