From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Uwe Kleine-K??nig <Uwe.Kleine-Koenig@digi.com>
Cc: linux-input@vger.kernel.org, Dmitry Baryshkov <dbaryshkov@gmail.com>
Subject: Re: [PATCH] Input: gpio-keys - fix possible NULL pointer dereference
Date: Wed, 30 Jul 2008 10:53:03 -0400 [thread overview]
Message-ID: <20080730104856.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <1217424431-8732-1-git-send-email-Uwe.Kleine-Koenig@digi.com>
Hi Uwe,
On Wed, Jul 30, 2008 at 03:27:10PM +0200, Uwe Kleine-K??nig wrote:
> bdata->button is used in gpio_check_button but never initialized. Having a
> device with debounce_interval != 0 without this patch resulted on an oops on
> my machine.
>
Applied both patches to 'for-linus' branch, thanks!
--
Dmitry
prev parent reply other threads:[~2008-07-30 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 13:27 [PATCH] Input: gpio-keys - fix possible NULL pointer dereference Uwe Kleine-König
2008-07-30 13:27 ` [PATCH] Input: gpio-keys - make gpio_keys_device_driver static Uwe Kleine-König
2008-07-30 13:32 ` [PATCH] Input: gpio-keys - fix possible NULL pointer dereference Uwe Kleine-König
2008-07-30 14:53 ` Dmitry Torokhov [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=20080730104856.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Uwe.Kleine-Koenig@digi.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).