From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Dan Carpenter <error27@gmail.com>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
Richard Purdie <rpurdie@linux.intel.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] input: error handling bug in lm8323_probe()
Date: Tue, 29 Jun 2010 07:07:01 +0000 [thread overview]
Message-ID: <20100629070701.GB19712@core.coreip.homeip.net> (raw)
In-Reply-To: <20100610075431.GK5483@bicker>
On Thu, Jun 10, 2010 at 09:54:31AM +0200, Dan Carpenter wrote:
> We reuse the "i" variable later on so if we goto fail3 or fail4 then "i"
> will be set to the wrong thing and cause a crash.
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
>
Applied to next, thanks Dan.
--
Dmitry
prev parent reply other threads:[~2010-06-29 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 7:54 [patch] input: error handling bug in lm8323_probe() Dan Carpenter
2010-06-29 7:07 ` 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=20100629070701.GB19712@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=rpurdie@linux.intel.com \
--cc=w.sang@pengutronix.de \
/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