public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] istallion: add missing __devexit marking
Date: Tue, 19 May 2009 15:35:16 +1000	[thread overview]
Message-ID: <4A124514.2090609@snapgear.com> (raw)
In-Reply-To: <1242632850-16268-1-git-send-email-vapier@gentoo.org>

Hi Mike,

Mike Frysinger wrote:
> The remove member of the pci_driver stli_pcidriver uses __devexit_p(),
> so the remove function itself should be marked with __devexit.  Even
> more so considering the probe function is marked with __devinit.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> CC: Greg Ungerer <gerg@uclinux.org>

Looks ok to me:

Acked-by: Greg Ungerer <gerg@uclinux.org>


> ---
>  drivers/char/istallion.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/char/istallion.c b/drivers/char/istallion.c
> index fff19f7..e8392c2 100644
> --- a/drivers/char/istallion.c
> +++ b/drivers/char/istallion.c
> @@ -3785,7 +3785,7 @@ err:
>  	return retval;
>  }
>  
> -static void stli_pciremove(struct pci_dev *pdev)
> +static void __devexit stli_pciremove(struct pci_dev *pdev)
>  {
>  	struct stlibrd *brdp = pci_get_drvdata(pdev);
>  

-- 
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

      reply	other threads:[~2009-05-19  5:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18  7:47 [PATCH] istallion: add missing __devexit marking Mike Frysinger
2009-05-19  5:35 ` Greg Ungerer [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=4A124514.2090609@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier@gentoo.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