From: Michal Marek <mmarek@suse.cz>
To: Kirill Smelkov <kirr@mns.spb.ru>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: fix a couple of typos in Documentation
Date: Wed, 17 Feb 2010 14:18:07 +0100 [thread overview]
Message-ID: <4B7BEC8F.8090207@suse.cz> (raw)
In-Reply-To: <1266396333-6916-1-git-send-email-kirr@mns.spb.ru>
On 17.2.2010 09:45, Kirill Smelkov wrote:
> Signed-off-by: Kirill Smelkov <kirr@mns.spb.ru>
> ---
> Documentation/kbuild/kbuild.txt | 2 +-
> Documentation/kbuild/makefiles.txt | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/kbuild/kbuild.txt b/Documentation/kbuild/kbuild.txt
> index 6f8c1ca..84725b7 100644
> --- a/Documentation/kbuild/kbuild.txt
> +++ b/Documentation/kbuild/kbuild.txt
> @@ -65,7 +65,7 @@ CROSS_COMPILE
> Specify an optional fixed part of the binutils filename.
> CROSS_COMPILE can be a part of the filename or the full path.
>
> -CROSS_COMPILE is also used for ccache is some setups.
> +CROSS_COMPILE is also used for ccache in some setups.
>
> CF
> --------------------------------------------------
> diff --git a/Documentation/kbuild/makefiles.txt b/Documentation/kbuild/makefiles.txt
> index 71c602d..0135155 100644
> --- a/Documentation/kbuild/makefiles.txt
> +++ b/Documentation/kbuild/makefiles.txt
> @@ -320,7 +320,7 @@ more details, with real examples.
> subdir-ccflags-y, subdir-asflags-y
> The two flags listed above are similar to ccflags-y and as-falgs-y.
> The difference is that the subdir- variants has effect for the kbuild
> - file where tey are present and all subdirectories.
> + file where they are present and all subdirectories.
> Options specified using subdir-* are added to the commandline before
> the options specified using the non-subdir variants.
Applied, thanks.
Michal
prev parent reply other threads:[~2010-02-17 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 8:45 [PATCH] kbuild: fix a couple of typos in Documentation Kirill Smelkov
2010-02-17 13:18 ` Michal Marek [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=4B7BEC8F.8090207@suse.cz \
--to=mmarek@suse.cz \
--cc=kirr@mns.spb.ru \
--cc=linux-kbuild@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 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.