public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Warren Turkal <wt@penguintechs.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: possible typo
Date: Mon, 09 Jun 2014 01:07:04 -0700	[thread overview]
Message-ID: <53956B28.7040404@penguintechs.org> (raw)
In-Reply-To: <20140609074630.GA15826@ravnborg.org>

commit 4ce2f36b4b06b7df569b1875c7ab834270786882
Author: Warren Turkal <wt@penguintechs.org>
Date:   Sun Jun 8 22:19:29 2014 -0700

     Fix a typo.

     Signed-off-by: Warren Turkal <wt@penguintechs.org>

diff --git a/Documentation/kbuild/modules.txt 
b/Documentation/kbuild/modules.txt
index 69372fb..3fb39e0 100644
--- a/Documentation/kbuild/modules.txt
+++ b/Documentation/kbuild/modules.txt
@@ -470,7 +470,7 @@ build.

  	Sometimes, an external module uses exported symbols from
  	another external module. kbuild needs to have full knowledge of
-	all symbols to avoid spliitting out warnings about undefined
+	all symbols to avoid spitting out warnings about undefined
  	symbols. Three solutions exist for this situation.

  	NOTE: The method with a top-level kbuild file is recommended

wt

On 06/09/2014 12:46 AM, Sam Ravnborg wrote:
> On Sun, Jun 08, 2014 at 10:40:55PM -0700, Warren Turkal wrote:
>> Hey,
>>
>> I think I found a typo in the kbuild docs. A one line commit can be pulled
>> from the "fix_typo" branch from the git repo @ git@github.com:wt/linux.git.
>>
>> Can someone please take a look at this branch at some point?
> No.
> Please submit this as a regular patch - see Documentation/SubmittingPatches
>
> 	Sam
>

       reply	other threads:[~2014-06-09  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <539548E7.9070908@penguintechs.org>
     [not found] ` <20140609074630.GA15826@ravnborg.org>
2014-06-09  8:07   ` Warren Turkal [this message]
2014-06-10  0:29     ` possible typo Randy Dunlap
2014-06-10 12:16     ` Michal Marek

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=53956B28.7040404@penguintechs.org \
    --to=wt@penguintechs.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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