All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: fix a typo in a kbuild document
Date: Thu, 12 Jun 2014 10:24:00 +0900	[thread overview]
Message-ID: <20140612102400.9635.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <1402385774-3748-1-git-send-email-yamada.m@jp.panasonic.com>

Hi Michal,

Does this patch look good?

If it is not too late,
could you consider to include this trivial one in your GIT-PULL?



On Tue, 10 Jun 2014 16:36:14 +0900
Masahiro Yamada <yamada.m@jp.panasonic.com> wrote:

> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> ---
>  Documentation/kbuild/makefiles.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/kbuild/makefiles.txt b/Documentation/kbuild/makefiles.txt
> index d567a7c..c600e2f 100644
> --- a/Documentation/kbuild/makefiles.txt
> +++ b/Documentation/kbuild/makefiles.txt
> @@ -1171,7 +1171,7 @@ When kbuild executes, the following steps are followed (roughly):
>  	      obvious reason.
>  
>      dtc
> -	Create flattend device tree blob object suitable for linking
> +	Create flattened device tree blob object suitable for linking
>  	into vmlinux. Device tree blobs linked into vmlinux are placed
>  	in an init section in the image. Platform code *must* copy the
>  	blob to non-init memory prior to calling unflatten_device_tree().
> -- 
> 1.9.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2014-06-12  1:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  7:36 [PATCH] kbuild: fix a typo in a kbuild document Masahiro Yamada
2014-06-12  1:24 ` Masahiro Yamada [this message]
2014-06-12  8:28   ` Michal Marek
2014-06-18 19:39     ` 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=20140612102400.9635.AA925319@jp.panasonic.com \
    --to=yamada.m@jp.panasonic.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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.