From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Viresh Kumar <viresh.kumar@st.com>
Cc: swarren@nvidia.com, olof@lixom.net, linux-input@vger.kernel.org,
srasal@nvidia.com
Subject: Re: [PATCH] Input: tegra-kbc: Fix: Allocate pdata before using it
Date: Mon, 26 Mar 2012 23:47:25 -0700 [thread overview]
Message-ID: <20120327064725.GA1361@core.coreip.homeip.net> (raw)
In-Reply-To: <28d8716b43c5078b238638ba60a4b170807074b9.1332827588.git.viresh.kumar@st.com>
On Tue, Mar 27, 2012 at 11:24:49AM +0530, Viresh Kumar wrote:
> Following commit broke DT support for tegra-kbc by removing pdata allocation
> completely.
Must be my fat fingers, sorry about this.
>
> commit 023cea0ecfa2df034096c3f4afa796a0b2d1188a
> Author: Shridhar Rasal <srasal@nvidia.com>
> Date: Fri Feb 3 00:27:30 2012 -0800
>
> Input: tegra-kbc - allow skipping setting up some of GPIO pins
>
> This patch restores it.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> ---
> drivers/input/keyboard/tegra-kbc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/input/keyboard/tegra-kbc.c b/drivers/input/keyboard/tegra-kbc.c
> index 96ee31e..5827fbe 100644
> --- a/drivers/input/keyboard/tegra-kbc.c
> +++ b/drivers/input/keyboard/tegra-kbc.c
> @@ -630,6 +630,7 @@ tegra_kbc_dt_parse_pdata(struct platform_device *pdev)
> if (!np)
> return NULL;
>
> + pdata = kzalloc(sizeof(*pdata), GFP_KERNEL);
> if (!pdata)
> return NULL;
>
> --
> 1.7.10.rc2.10.gb47606
>
--
Dmitry
next prev parent reply other threads:[~2012-03-27 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 5:54 [PATCH] Input: tegra-kbc: Fix: Allocate pdata before using it Viresh Kumar
2012-03-27 6:47 ` Dmitry Torokhov [this message]
2012-03-27 6:48 ` Viresh Kumar
2012-03-27 6:55 ` Dmitry Torokhov
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=20120327064725.GA1361@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=olof@lixom.net \
--cc=srasal@nvidia.com \
--cc=swarren@nvidia.com \
--cc=viresh.kumar@st.com \
/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