From: Timo Hoenig <thoenig-dCxI//HcOdFeoWH0uzbU5w@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Sascha Sommer
<saschasommer-KuiJ5kEpwI6ELgA04lAiVw@public.gmane.org>
Subject: Re: asus_acpi oops on samsung p35
Date: Tue, 29 Nov 2005 10:09:16 +0100 [thread overview]
Message-ID: <1133255356.25720.19.camel@linux.site> (raw)
In-Reply-To: <200511251443.19125.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Hi,
On Fri, 2005-11-25 at 14:43 +0800, Yu, Luming wrote:
> On Tuesday 22 November 2005 03:38, Sascha Sommer wrote:
> > Hi,
> >
> > as the oops, reported for example in
> > http://sourceforge.net/mailarchive/message.php?msg_id=11977633,
> > is still occuring on recent kernels it would be nice if someone could
> > review the attached patch from Christian Aichinger posted to this list in
> > http://sourceforge.net/mailarchive/message.php?msg_id=13057151
> > so the remaining issues can be fixed.
> > It is working fine with my Samsung p35.
>
> One question: why you need asus_acpi.c ?
>
> Does striking hotkeys on keyboard works for you?
> Do you need to echo something to proc files
> for hotkey function?
Please include the fix as asus_acpi.c is still part of the mainline
kernel.
The fix is extensively tested. I've included a similar patch for SL
10.0 and had positive feedback of Samsung P3x users. It did not bear
any side effects.
> Thanks,
> Luming
Thanks,
Timo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
prev parent reply other threads:[~2005-11-29 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 19:38 asus_acpi oops on samsung p35 Sascha Sommer
[not found] ` <200511212038.39593.saschasommer-KuiJ5kEpwI6ELgA04lAiVw@public.gmane.org>
2005-11-25 6:43 ` Yu, Luming
[not found] ` <200511251443.19125.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2005-11-26 11:25 ` Sascha Sommer
2005-11-29 9:09 ` Timo Hoenig [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=1133255356.25720.19.camel@linux.site \
--to=thoenig-dcxi//hcodfeowh0uzbu5w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=saschasommer-KuiJ5kEpwI6ELgA04lAiVw@public.gmane.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