From: Randy Dunlap <rdunlap@infradead.org>
To: Warren Turkal <wt@penguintechs.org>, 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 17:29:48 -0700 [thread overview]
Message-ID: <5396517C.4070108@infradead.org> (raw)
In-Reply-To: <53956B28.7040404@penguintechs.org>
On 06/09/14 01:07, Warren Turkal wrote:
> 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>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> 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
--
~Randy
next prev parent reply other threads:[~2014-06-10 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 5:40 possible typo Warren Turkal
2014-06-09 7:46 ` Sam Ravnborg
2014-06-09 8:07 ` Warren Turkal
2014-06-10 0:29 ` Randy Dunlap [this message]
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=5396517C.4070108@infradead.org \
--to=rdunlap@infradead.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 \
--cc=wt@penguintechs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.