Linux Input/HID development
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	David Brownell <dbrownell@users.sourceforge.net>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: twl4030_keypad - fix potential NULL dereference in twl4030_kp_probe()
Date: Fri, 1 Apr 2011 18:18:44 +0300	[thread overview]
Message-ID: <20110401151843.GB2164@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1301670483.6013.4.camel@phoenix>

On Fri, Apr 01, 2011 at 11:08:03PM +0800, Axel Lin wrote:
> We should first check whether platform data is NULL or not, before
> dereferencing it to get the keymap.
> 
> Signed-off-by: Axel Lin <axel.lin@gmail.com>

Reviewed-by: Felipe Balbi <balbi@ti.com>

-- 
balbi

      reply	other threads:[~2011-04-01 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 15:08 [PATCH] Input: twl4030_keypad - fix potential NULL dereference in twl4030_kp_probe() Axel Lin
2011-04-01 15:18 ` Felipe Balbi [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=20110401151843.GB2164@legolas.emea.dhcp.ti.com \
    --to=balbi@ti.com \
    --cc=axel.lin@gmail.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --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