public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: linux-kernel@vger.kernel.org
Cc: Ben Dooks <ben-linux@fluff.org>
Subject: scripts/mod/modpost.c: fix spelling of module and happens]
Date: Tue, 15 Jul 2008 21:53:57 +0100	[thread overview]
Message-ID: <20080715205357.240969925@fluff.org.uk> (raw)

[-- Attachment #1: simtec/simtec-modpost-spello-fix.patch --]
[-- Type: text/plain, Size: 1068 bytes --]

Spelling fixes in scripts/mod/modpost.c

Signed-off-by: Ben Dooks <ben-linux@fluff.org>

Index: linux-2.6.26-quilt2/scripts/mod/modpost.c
===================================================================
--- linux-2.6.26-quilt2.orig/scripts/mod/modpost.c	2008-07-15 21:52:19.000000000 +0100
+++ linux-2.6.26-quilt2/scripts/mod/modpost.c	2008-07-15 21:52:40.000000000 +0100
@@ -1468,7 +1468,7 @@ static void section_rel(const char *modn
  * marked __initdata will be discarded when the module has been intialized.
  * Likewise for modules used built-in the sections marked __exit
  * are discarded because __exit marked function are supposed to be called
- * only when a moduel is unloaded which never happes for built-in modules.
+ * only when a module is unloaded which never happens for built-in modules.
  * The check_sec_ref() function traverses all relocation records
  * to find all references to a section that reference a section that will
  * be discarded and warns about it.

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

             reply	other threads:[~2008-07-15 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 20:53 Ben Dooks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-29  0:05 scripts/mod/modpost.c: fix spelling of module and happens] Ben Dooks

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=20080715205357.240969925@fluff.org.uk \
    --to=ben-linux@fluff.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