From: Ian Abbott <abbotti@mev.co.uk>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Ian Abbott <ian.abbott@mev.co.uk>,
Mori Hess <fmhess@users.sourceforge.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging/comedi: Move comedi_pci_auto_unconfig to drivers.c
Date: Thu, 24 Jan 2013 10:02:35 +0000 [thread overview]
Message-ID: <510106BB.2080709@mev.co.uk> (raw)
In-Reply-To: <1358895810-27115-1-git-send-email-peterhuewe@gmx.de>
On 2013-01-22 23:03, Peter Huewe wrote:
> Since comedi_pci_auto_unconfig cannot be inlined anymore after
> staging/comedi: Use comedi_pci_auto_unconfig directly for
> pci_driver.remove
> is applied, it makes sense to move it drivers.c
>
> Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
> ---
> drivers/staging/comedi/comedidev.h | 5 +----
> drivers/staging/comedi/drivers.c | 6 ++++++
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/comedi/comedidev.h b/drivers/staging/comedi/comedidev.h
> index 6211d44..e2b7d60 100644
> --- a/drivers/staging/comedi/comedidev.h
> +++ b/drivers/staging/comedi/comedidev.h
> @@ -484,10 +484,7 @@ static inline int comedi_pci_auto_config(struct pci_dev *pcidev,
> return comedi_auto_config(&pcidev->dev, driver, 0);
> }
>
> -static inline void comedi_pci_auto_unconfig(struct pci_dev *pcidev)
> -{
> - comedi_auto_unconfig(&pcidev->dev);
> -}
> +void comedi_pci_auto_unconfig(struct pci_dev *pcidev);
>
> static inline int comedi_usb_auto_config(struct usb_interface *intf,
> struct comedi_driver *driver)
> diff --git a/drivers/staging/comedi/drivers.c b/drivers/staging/comedi/drivers.c
> index 1c7d4da..87eeee5 100644
> --- a/drivers/staging/comedi/drivers.c
> +++ b/drivers/staging/comedi/drivers.c
> @@ -558,6 +558,12 @@ void comedi_pci_driver_unregister(struct comedi_driver *comedi_driver,
> }
> EXPORT_SYMBOL_GPL(comedi_pci_driver_unregister);
>
> +void comedi_pci_auto_unconfig(struct pci_dev *pcidev)
> +{
> + comedi_auto_unconfig(&pcidev->dev);
> +}
> +EXPORT_SYMBOL_GPL(comedi_pci_auto_unconfig);
> +
> #if IS_ENABLED(CONFIG_PCMCIA)
> int comedi_pcmcia_driver_register(struct comedi_driver *comedi_driver,
> struct pcmcia_driver *pcmcia_driver)
>
Embarassingly (for me) I submitted a patch to do the exact opposite
previously, but I've no problem doing it this way if it saves some code.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2013-01-24 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 22:40 [PATCH] staging/comedi: Use comedi_pci_auto_unconfig directly for pci_driver.remove Peter Huewe
2013-01-22 22:49 ` H Hartley Sweeten
2013-01-22 23:02 ` Peter Hüwe
2013-01-22 23:03 ` [PATCH] staging/comedi: Move comedi_pci_auto_unconfig to drivers.c Peter Huewe
2013-01-24 10:02 ` Ian Abbott [this message]
2013-01-24 21:30 ` Peter Huewe
2013-01-25 10:58 ` Ian Abbott
2013-01-25 20:09 ` Greg Kroah-Hartman
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=510106BB.2080709@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=ian.abbott@mev.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.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