From: Greg KH <greg@kroah.com>
To: Eugeni Dodonov <eugeni@mandriva.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: asus_oled oops in 2.6.32.2
Date: Wed, 23 Dec 2009 09:49:42 -0800 [thread overview]
Message-ID: <20091223174941.GA20331@kroah.com> (raw)
In-Reply-To: <4B320CAA.1030708@mandriva.com>
On Wed, Dec 23, 2009 at 10:27:22AM -0200, Eugeni Dodonov wrote:
> Hi,
>
> After updating to 2.6.32 kernel, I started experiencing Oopses caused by
> the asus_oled module. After quick investigation, I wrapped this simple
> patch which fixes an Oops in by asus_oled module on 2.6.32.2 kernel,
> caused by incorrect usage of strict_strtoul function call within
> set_enabled and set_disabled functions. This can be triggered by simple
> running the userspace client for asus_old (e.g., 'asusoled -e' or
> 'asusoled -d').
Looks good, can I get a 'Signed-off-by:' line so that I can apply the
patch?
thanks,
greg k-h
next prev parent reply other threads:[~2009-12-23 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 12:27 PATCH: asus_oled oops in 2.6.32.2 Eugeni Dodonov
2009-12-23 17:49 ` Greg KH [this message]
2009-12-23 20:02 ` Eugeni Dodonov
2010-01-15 18:06 ` Greg KH
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=20091223174941.GA20331@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=eugeni@mandriva.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@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