From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] ARM: keystone2: Split monitor code / command code
Date: Wed, 16 Mar 2016 18:15:19 +0100 [thread overview]
Message-ID: <20160316181519.0320fa06@lilith> (raw)
In-Reply-To: <1458140588-28276-1-git-send-email-trini@konsulko.com>
Hello Tom,
On Wed, 16 Mar 2016 11:03:03 -0400, Tom Rini <trini@konsulko.com> wrote:
> When we switch to including all linker lists in U-Boot it is important
> to not include commands as that may lead to link errors due to other
> things we have already discarded. In this case, we split the code for
> supporting the monitor out from the code for loading it.
Not sure I'm understanding this commit message. Can you clarify?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2016-03-16 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 15:03 [U-Boot] [PATCH 1/6] ARM: keystone2: Split monitor code / command code Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 2/6] ARM: keystone2: Switch to using the poweroff command Tom Rini
2016-03-17 1:56 ` Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 3/6] ARM: keystone2: Only link cmd_ddr3.o on non-SPL builds Tom Rini
2016-03-17 1:56 ` Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 4/6] cmd: scsi: Group the command portion together, guard with !CONFIG_SPL_BUILD Tom Rini
2016-03-17 1:57 ` Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 5/6] lpc32xx: work_92105: Rework Makefile Tom Rini
2016-03-17 1:57 ` Tom Rini
2016-03-16 15:03 ` [U-Boot] [PATCH 6/6] arm: omap-common: Guard some parts of the code with CONFIG_OMAP44XX/OMAP54XX Tom Rini
2016-03-17 1:57 ` Tom Rini
2016-03-16 17:15 ` Albert ARIBAUD [this message]
2016-03-16 19:02 ` [U-Boot] [PATCH 1/6] ARM: keystone2: Split monitor code / command code Tom Rini
2016-03-17 1:56 ` Tom Rini
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=20160316181519.0320fa06@lilith \
--to=albert.u.boot@aribaud.net \
--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.