All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] kbuild: create a build directory automatically for out-of-tree build
Date: Fri, 28 Mar 2014 17:16:49 -0400	[thread overview]
Message-ID: <20140328211649.GI16360@bill-the-cat> (raw)
In-Reply-To: <1395636927-11294-1-git-send-email-yamada.m@jp.panasonic.com>

On Mon, Mar 24, 2014 at 01:55:27PM +0900, Masahiro Yamada wrote:

> Prior to Kbuild, the build system created a build directory,
> when it did not exist, for out-of-tree build.
> 
> This feature was dropped when we switched to Kbuild
> because many of lines in makefiles were copied from Linux Kernel.
> (In Linux Kernel, we have to create a build directory by ourselves
> before starting build.)
> 
> That feature seems worth reviving for less typing
> even if our code and Linux Kernel diverge.
> 
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Suggested-by: Simon Glass <sjg@chromium.org>
> Acked-by: Simon Glass <sjg@chromium.org>
> Tested-by: Simon Glass <sjg@chromium.org>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140328/52ab2212/attachment.pgp>

      parent reply	other threads:[~2014-03-28 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  4:55 [U-Boot] [PATCH] kbuild: create a build directory automatically for out-of-tree build Masahiro Yamada
2014-03-24 23:41 ` Simon Glass
2014-03-27 17:20   ` Tom Rini
2014-03-28  2:37     ` Masahiro Yamada
2014-03-28  2:43       ` Simon Glass
2014-04-15  4:38       ` Masahiro Yamada
2014-03-28 21:16 ` Tom Rini [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=20140328211649.GI16360@bill-the-cat \
    --to=trini@ti.com \
    --cc=u-boot@lists.denx.de \
    /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.