From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Build system: Don't check for CONFIG_SYS_TEXT_BASE being set
Date: Thu, 1 Feb 2018 00:18:53 +0900 [thread overview]
Message-ID: <CAK7LNATE5+2_+YMSExaxL64dYMywQZ3H90WQ-pZZRhUchH7jqA@mail.gmail.com> (raw)
In-Reply-To: <1517329684.4754.1.camel@synopsys.com>
2018-01-31 1:28 GMT+09:00 Alexey Brodkin <Alexey.Brodkin@synopsys.com>:
> Hi MAsahiro-san, Tom,
>
> On Wed, 2018-01-31 at 01:23 +0900, Masahiro Yamada wrote:
>> 2018-01-31 0:23 GMT+09:00 Alexey Brodkin <Alexey.Brodkin@synopsys.com>:
>> >
>> Please feel free to include historical reason:
>>
>> This ifneq conditional was added for Blackfin because it did not use
>> CONFIG_SYS_TEXT_BASE.
>> See.
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_u-2Dboot_u-2Dboot_blob_v2017.03_arch_blackfin_config.mk-23L67&d=DwIBaQ&c=DPL6_X_6JkX
>> Fx7AXWqB0tg&r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=mezwGj3E5EIPuE8Oln2gVeTJ-8q19KNepz7Jo-
>> Kcu1o&s=dmnDXQ05QLyAFKUgnsVyJOS8aybk3rhbDNsgiio6zvA&e=
>>
>> Then Blackfin is gone, so should be OK.
>
> Should I send a respin with this valuable addition or whoever's going to apply will
> fix-up this?
>
> -Alexey
Either will do for me.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2018-01-31 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 15:23 [U-Boot] [PATCH] Build system: Don't check for CONFIG_SYS_TEXT_BASE being set Alexey Brodkin
2018-01-30 16:23 ` Masahiro Yamada
2018-01-30 16:28 ` Alexey Brodkin
2018-01-31 15:18 ` Masahiro Yamada [this message]
2018-01-31 15:21 ` Alexey Brodkin
2018-02-02 15:01 ` Masahiro Yamada
2018-02-11 20:47 ` [U-Boot] " Tom Rini
2018-02-12 13:27 ` Alexey Brodkin
2018-02-12 14:23 ` Tom Rini
2018-02-12 14:46 ` Marek Vasut
2018-02-12 16:21 ` Alexey Brodkin
2018-02-12 16:29 ` Tom Rini
2018-02-12 20:48 ` Max Filippov
2018-02-12 21:03 ` Tom Rini
2018-02-12 21:48 ` Max Filippov
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=CAK7LNATE5+2_+YMSExaxL64dYMywQZ3H90WQ-pZZRhUchH7jqA@mail.gmail.com \
--to=yamada.masahiro@socionext.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.