From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] __FILE__ usage and and SPL limits for SRAM
Date: Wed, 31 May 2017 07:32:23 -0400 [thread overview]
Message-ID: <20170531113223.GW10782@bill-the-cat> (raw)
In-Reply-To: <CAK7LNAQjFghUNCGDLWAcqoVxaw=TGSoa5ZQ706JwSo1NfAb9dw@mail.gmail.com>
On Wed, May 31, 2017 at 01:51:30PM +0900, Masahiro Yamada wrote:
> Hi Tom
>
> 2017-05-23 10:27 GMT+09:00 Tom Rini <trini@konsulko.com>:
>
> >> >
> >> > <snip>
> >> >
> >> >> I can do this, but
> >> >> I'd like to move forward synced with Linux.
> >> >>
> >> >>
> >> >> Yesterday, I took some time to write patches
> >> >> and sent them to Linux ML.
> >> >>
> >> >>
> >> >> Plan A:
> >> >> https://lkml.org/lkml/2017/4/21/623
> >> >> https://patchwork.kernel.org/patch/9693559/
> >> >> https://patchwork.kernel.org/patch/9693563/
> >> >>
> >> >>
> >> >> Plan B:
> >> >> https://patchwork.kernel.org/patch/9693623/
> >> >
> >> > FWIW:
> >> >
> >> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70268
> >>
> >> Thanks for you pointer!
> >>
> >> If merged, it will reduce the image size, and also helpful for
> >> reproducible build.
> >>
> >> (We can not save users of old GCC versions, though...)
> >
> > Did the kernel side of this die out? Thanks!
>
>
> It did not.
> At least, I got some positive comments,
> but I am still wondering what the best approach would be.
Plan A got the positive feedback. I'd be happy to have U-Boot trial
that out so you can post a non-RFC to the kernel and say we've used it
and ironed out any issues, if some arise.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170531/a6ed590e/attachment.sig>
next prev parent reply other threads:[~2017-05-31 11:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 21:44 [U-Boot] __FILE__ usage and and SPL limits for SRAM Nishanth Menon
2017-03-28 6:07 ` Lokesh Vutla
2017-04-04 19:06 ` Tom Rini
2017-04-05 11:27 ` Wolfgang Denk
2017-04-09 19:27 ` Simon Glass
2017-04-22 5:30 ` Masahiro Yamada
2017-05-22 17:23 ` Denys Dmytriyenko
2017-05-23 0:57 ` Masahiro Yamada
2017-05-23 1:27 ` Tom Rini
2017-05-31 4:51 ` Masahiro Yamada
2017-05-31 11:32 ` Tom Rini [this message]
2017-03-28 6:29 ` Masahiro Yamada
2017-03-28 11:20 ` Nishanth Menon
2017-03-28 11:47 ` Felipe Balbi
2017-03-28 11:59 ` Nishanth Menon
2017-03-29 10:57 ` Masahiro Yamada
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=20170531113223.GW10782@bill-the-cat \
--to=trini@konsulko.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.