public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manohar Vanga <manohar.vanga@cern.ch>
To: <martyn.welch@ge.com>
Cc: <cota@braap.org>, <devel@driverdev.osuosl.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Staging: vme: fix potential infinite loop
Date: Wed, 23 Feb 2011 10:24:24 +0100	[thread overview]
Message-ID: <20110223092424.GA5195@athena> (raw)
In-Reply-To: <1298403376-28352-3-git-send-email-manohar.vanga@cern.ch>

On Tue, Feb 22, 2011 at 08:36:16PM +0100, Manohar Vanga wrote:
> Fix a bug in vme_register_bridge that resulted in an infinite loop if
> device_register failed.
> 
> Signed-off-by: Manohar Vanga <manohar.vanga@cern.ch>
> ---
>  drivers/staging/vme/vme.c |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/staging/vme/vme.c b/drivers/staging/vme/vme.c
> index 88bf455..7eb4568 100644
> --- a/drivers/staging/vme/vme.c
> +++ b/drivers/staging/vme/vme.c
> @@ -1364,9 +1364,14 @@ int vme_register_bridge(struct vme_bridge *bridge)
>  	return retval;
>  
>  err_reg:
> +	/*
> +	 * Ignore the failed driver and unregister the rest
> +	 */
> +	i--

Ugh. Missing semicolon here. I'll resend the corrected patch.

Thanks,
Manohar Vanga

      parent reply	other threads:[~2011-02-23  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1298403376-28352-1-git-send-email-manohar.vanga@cern.ch>
     [not found] ` <1298403376-28352-2-git-send-email-manohar.vanga@cern.ch>
2011-02-23  9:19   ` [PATCH 1/2] Staging: vme: remove unreachable code Martyn Welch
2011-02-23 12:17     ` Dan Carpenter
2011-02-23 15:09       ` Martyn Welch
2011-02-23 15:16         ` Manohar Vanga
2011-02-23 15:19           ` Martyn Welch
     [not found] ` <1298403376-28352-3-git-send-email-manohar.vanga@cern.ch>
2011-02-23  9:24   ` Manohar Vanga [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=20110223092424.GA5195@athena \
    --to=manohar.vanga@cern.ch \
    --cc=cota@braap.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martyn.welch@ge.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