All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: greg@kroah.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: vme: Fix warning in free_irq for ca91cx42
Date: Wed, 27 Oct 2010 11:42:40 +0100	[thread overview]
Message-ID: <4CC80220.6010609@ge.com> (raw)
In-Reply-To: <20101027103806.2783.47604.stgit@ES-BJ21R4J>

Greg,

Please dis-regard this patch - trying to do to many things at once leads
to mistakes...

Martyn

On 27/10/10 11:38, Martyn Welch wrote:
> As discovered by Emilio Cota for the tsi148, the cookie passed to request_irq
> isn't the same as the one passed to free_irq.
> 
> Fix it by passing the same cookie to both functions.
> 
> Signed-off-by: Martyn Welch <martyn.welch@ge.com>
> ---
> 
>  drivers/staging/vme/bridges/vme_ca91cx42.c |   10 ++++++----
>  1 files changed, 6 insertions(+), 4 deletions(-)
> 
> 
> diff --git a/drivers/staging/vme/bridges/vme_ca91cx42.c b/drivers/staging/vme/bridges/vme_ca91cx42.c
> index 1f2089f..5f7f458 100644
> --- a/drivers/staging/vme/bridges/vme_ca91cx42.c
> +++ b/drivers/staging/vme/bridges/vme_ca91cx42.c
> @@ -242,9 +242,11 @@ static int ca91cx42_irq_init(struct vme_bridge *ca91cx42_bridge)
>  	return 0;
>  }
>  
> -static void ca91cx42_irq_exit(struct ca91cx42_driver *bridge,
> +static void ca91cx42_irq_exit(struct vme_driver *ca91cx42_bridge,
>  	struct pci_dev *pdev)
>  {
> +	struct ca91cx42_driver *bridge = ca91cx42_bridge->driver_priv;
> +
>  	/* Disable interrupts from PCI to VME */
>  	iowrite32(0, bridge->base + VINT_EN);
>  
> @@ -253,7 +255,7 @@ static void ca91cx42_irq_exit(struct ca91cx42_driver *bridge,
>  	/* Clear Any Pending PCI Interrupts */
>  	iowrite32(0x00FFFFFF, bridge->base + LINT_STAT);
>  
> -	free_irq(pdev->irq, pdev);
> +	free_irq(pdev->irq, ca91cx42_bridge);
>  }
>  
>  /*
> @@ -1815,7 +1817,7 @@ err_master:
>  		kfree(master_image);
>  	}
>  
> -	ca91cx42_irq_exit(ca91cx42_device, pdev);
> +	ca91cx42_irq_exit(ca91cx42_bridge, pdev);
>  err_irq:
>  err_test:
>  	iounmap(ca91cx42_device->base);
> @@ -1899,7 +1901,7 @@ void ca91cx42_remove(struct pci_dev *pdev)
>  		kfree(master_image);
>  	}
>  
> -	ca91cx42_irq_exit(bridge, pdev);
> +	ca91cx42_irq_exit(ca91cx42_bridge, pdev);
>  
>  	iounmap(bridge->base);
>  
> 
> 
> --
> Martyn Welch (Principal Software Engineer)   |   Registered in England and
> GE Intelligent Platforms                     |   Wales (3828642) at 100
> T +44(0)127322748                            |   Barbirolli Square, Manchester,
> E martyn.welch@ge.com                        |   M2 3AB  VAT:GB 927559189
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/devel


-- 
Martyn Welch (Principal Software Engineer)   |   Registered in England and
GE Intelligent Platforms                     |   Wales (3828642) at 100
T +44(0)127322748                            |   Barbirolli Square,
Manchester,
E martyn.welch@ge.com                        |   M2 3AB  VAT:GB 927559189

      reply	other threads:[~2010-10-27 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 10:38 [PATCH] Staging: vme: Fix warning in free_irq for ca91cx42 Martyn Welch
2010-10-27 10:42 ` Martyn Welch [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=4CC80220.6010609@ge.com \
    --to=martyn.welch@ge.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.