mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: Bruno Premont <bonbons@linux-vserver.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hid: adding __init/__exit macros to twinhan.c
Date: Tue, 29 Sep 2009 13:58:38 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.00.0909291358280.9280@wotan.suse.de> (raw)
In-Reply-To: <200909290324.56042.PeterHuewe@gmx.de>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1095 bytes --]

On Tue, 29 Sep 2009, Peter Hüwe wrote:

> From: Peter Huewe <peterhuewe@gmx.de>
> 
> Trivial patch which adds the __init/__exit macros to the module_init/
> module_exit functions of the twinhan driver in hid.
> 
> Jiri, I guess this time you can decide wether it's the hid or the trivial 
> tree ;) - thanks jiri for all your patience and work!
> 
> linux version v2.6.32-rc1 - linus git tree, Di 29. Sep 01:10:18 CEST 2009
> 
> Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
> ---
> diff --git a/drivers/hid/hid-twinhan.c b/drivers/hid/hid-twinhan.c
> index b05f602..c40afc5 100644
> --- a/drivers/hid/hid-twinhan.c
> +++ b/drivers/hid/hid-twinhan.c
> @@ -132,12 +132,12 @@ static struct hid_driver twinhan_driver = {
>  	.input_mapping = twinhan_input_mapping,
>  };
>  
> -static int twinhan_init(void)
> +static int __init twinhan_init(void)
>  {
>  	return hid_register_driver(&twinhan_driver);
>  }
>  
> -static void twinhan_exit(void)
> +static void __exit twinhan_exit(void)
>  {
>  	hid_unregister_driver(&twinhan_driver);
>  }

Applied, thanks.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

      reply	other threads:[~2009-09-29 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29  1:24 Peter Hüwe
2009-09-29 11:58 ` Jiri Kosina [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=alpine.LSU.2.00.0909291358280.9280@wotan.suse.de \
    --to=jkosina@suse.cz \
    --cc=PeterHuewe@gmx.de \
    --cc=bonbons@linux-vserver.org \
    --cc=linux-input@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®