mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Jiri Kosina <trivial@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Felipe Balbi <balbi@ti.com>
Subject: [PATCH 2/2] init: drop trailing semicolon from module_init/module_exit
Date: Thu, 10 Mar 2011 15:26:33 +0200	[thread overview]
Message-ID: <1299763593-3356-2-git-send-email-balbi@ti.com> (raw)
In-Reply-To: <1299763593-3356-1-git-send-email-balbi@ti.com>

now that all drivers add ; to the end of module_init()
and module_exit(), we can safely remove it from the
definition.

Signed-off-by: Felipe Balbi <balbi@ti.com>
---
 include/linux/init.h |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/linux/init.h b/include/linux/init.h
index 577671c5..8532f7c 100644
--- a/include/linux/init.h
+++ b/include/linux/init.h
@@ -263,7 +263,7 @@ void __init parse_early_options(char *cmdline);
  * builtin) or at module insertion time (if a module).  There can only
  * be one per module.
  */
-#define module_init(x)	__initcall(x);
+#define module_init(x)	__initcall(x)
 
 /**
  * module_exit() - driver exit entry point
@@ -275,7 +275,7 @@ void __init parse_early_options(char *cmdline);
  * compiled into the kernel, module_exit() has no effect.
  * There can only be one per module.
  */
-#define module_exit(x)	__exitcall(x);
+#define module_exit(x)	__exitcall(x)
 
 #else /* MODULE */
 
-- 
1.7.4.rc2


  reply	other threads:[~2011-03-10 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 13:26 [PATCH 1/2] trivial: add missing ; at the end of module_init/module_exit Felipe Balbi
2011-03-10 13:26 ` Felipe Balbi [this message]
2011-06-16  9:37 [RESEND/PATCH 0/2] trivial patches Felipe Balbi
2011-06-16  9:45 ` [PATCH 1/2] trivial: add missing ; at the end of module_init/module_exit Felipe Balbi
2011-06-16  9:45   ` [PATCH 2/2] init: drop trailing semicolon from module_init/module_exit Felipe Balbi

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=1299763593-3356-2-git-send-email-balbi@ti.com \
    --to=balbi@ti.com \
    --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

all inboxes | Powered by JetHome®