From: Michael Buesch <mb@bu3sch.de>
To: Peter Huewe <PeterHuewe@gmx.de>
Cc: Jiri Kosina <trivial@kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] gpio: adding __init/__exit macros in drivers/gpio/bt8xxgpio.c
Date: Sun, 23 Aug 2009 00:06:57 +0000 [thread overview]
Message-ID: <200908230206.57937.mb@bu3sch.de> (raw)
In-Reply-To: <200908230201.10471.PeterHuewe@gmx.de>
On Sunday 23 August 2009 02:01:10 Peter Huewe wrote:
> From: Peter Huewe <peterhuewe@gmx.de>
>
> Trivial patch which adds the __init/__exit macro to the init/exit functions of
> drivers/gpio/bt8xxgpio.c
>
> Michael, Kay or Greg, please have a look at the small patch and either pull it
> through your tree, or please ack' it so Jiri can pull it through the trivial
> tree.
>
> linux version 2.6.31-rc7 - linus git tree, So 23. Aug 01:38:43 CEST 2009
>
> Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
Acked-by: Michael Buesch <mb@bu3sch.de>
> ---
> diff --git a/drivers/gpio/bt8xxgpio.c b/drivers/gpio/bt8xxgpio.c
> index 984b587..5590414 100644
> --- a/drivers/gpio/bt8xxgpio.c
> +++ b/drivers/gpio/bt8xxgpio.c
> @@ -331,13 +331,13 @@ static struct pci_driver bt8xxgpio_pci_driver = {
> .resume = bt8xxgpio_resume,
> };
>
> -static int bt8xxgpio_init(void)
> +static int __init bt8xxgpio_init(void)
> {
> return pci_register_driver(&bt8xxgpio_pci_driver);
> }
> module_init(bt8xxgpio_init)
>
> -static void bt8xxgpio_exit(void)
> +static void __exit bt8xxgpio_exit(void)
> {
> pci_unregister_driver(&bt8xxgpio_pci_driver);
> }
>
>
--
Greetings, Michael.
next prev parent reply other threads:[~2009-08-23 0:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 0:01 [PATCH] gpio: adding __init/__exit macros in drivers/gpio/bt8xxgpio.c Peter Huewe
2009-08-23 0:06 ` Michael Buesch [this message]
2009-08-24 8:18 ` [PATCH] gpio: adding __init/__exit macros in Jiri Kosina
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=200908230206.57937.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=PeterHuewe@gmx.de \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).