From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] u-boot-sh/master
Date: Sat, 9 Feb 2019 07:46:01 -0500 [thread overview]
Message-ID: <20190209124601.GD16814@bill-the-cat> (raw)
In-Reply-To: <a5a85703-bbcc-6f2c-85a6-d0bfbacedba5@gmail.com>
On Sat, Feb 09, 2019 at 11:04:15AM +0100, Marek Vasut wrote:
> On 2/9/19 1:17 AM, Tom Rini wrote:
> > On Fri, Feb 08, 2019 at 11:19:46AM +0100, Marek Vasut wrote:
> >
> >> SD/MMC and filesystem fixes below ...
> >>
> >> The following changes since commit e5fd39c886485e3dec77f4438a6e364c2987cf5f:
> >>
> >> Merge tag 'for-master-20190201' of git://git.denx.de/u-boot-rockchip
> >> (2019-02-02 10:11:20 -0500)
> >>
> >> are available in the Git repository at:
> >>
> >> git://git.denx.de/u-boot-sh.git master
> >>
> >> for you to fetch changes up to 49f331023e1d6f804c4226b862af1f2a05a2ea2e:
> >>
> >> fs: ext4: Unmount FS in do_fs_type() (2019-02-06 14:07:12 +0100)
> >>
> >
> > NAK. The change:
> > commit 09a89b86d48a19598750f05f69412ec9ddbefba4
> > Author: Marek Vasut <marek.vasut+renesas@gmail.com>
> > Date: Tue Jan 29 04:45:51 2019 +0100
> >
> > mmc: Export {sd,mmc}_select_mode_and_width()
> >
> > breaks pine_h64 as SPL now overflows sram by 104 bytes.
>
> How is that even possible ?
OK, lets hack sunxi until it links again with these new functions, and
then use buildman to report code growth:
spl-u-boot-spl: add: 2/0, grow: 0/-1 bytes: 1264/-1100 (164)
function old new delta
sd_select_mode_and_width - 696 +696
mmc_select_mode_and_width - 568 +568
mmc_init 2280 1180 -1100
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190209/e2886625/attachment.sig>
next prev parent reply other threads:[~2019-02-09 12:46 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 10:19 [U-Boot] [PULL] u-boot-sh/master Marek Vasut
2019-02-09 0:17 ` Tom Rini
2019-02-09 10:04 ` Marek Vasut
2019-02-09 12:46 ` Tom Rini [this message]
2019-02-09 13:36 ` Marek Vasut
2019-02-09 23:11 ` Marek Vasut
2019-02-11 1:05 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2019-11-22 12:39 Marek Vasut
2019-11-22 22:15 ` Tom Rini
2019-10-05 16:20 Marek Vasut
2019-10-06 0:09 ` Tom Rini
2019-09-15 20:41 Marek Vasut
2019-09-16 11:21 ` Tom Rini
2019-09-07 17:31 Marek Vasut
2019-09-09 1:13 ` Tom Rini
2019-08-29 12:07 Marek Vasut
2019-08-31 13:28 ` Tom Rini
2019-08-31 13:37 ` Marek Vasut
2019-09-02 14:13 ` Tom Rini
2019-08-10 21:35 Marek Vasut
2019-08-11 1:13 ` Tom Rini
2019-07-30 12:07 Marek Vasut
2019-07-31 12:33 ` Tom Rini
2019-06-14 10:44 Marek Vasut
2019-06-17 15:19 ` Tom Rini
2019-05-26 23:14 Marek Vasut
2019-05-27 18:35 ` Tom Rini
2019-05-15 22:52 Marek Vasut
2019-05-17 11:15 ` Tom Rini
2019-05-11 23:54 Marek Vasut
2019-05-14 14:07 ` Tom Rini
2019-05-07 13:29 Marek Vasut
2019-05-07 18:13 ` Tom Rini
2019-05-05 19:18 Marek Vasut
2019-05-07 2:43 ` Tom Rini
2019-04-10 14:47 Marek Vasut
2019-04-11 22:15 ` Tom Rini
2019-04-02 1:16 Marek Vasut
2019-04-02 18:05 ` Tom Rini
2019-03-26 17:43 Marek Vasut
2019-03-29 1:24 ` Tom Rini
2019-03-10 13:26 Marek Vasut
2019-03-11 19:40 ` Tom Rini
2019-03-04 21:33 Marek Vasut
2019-03-05 2:48 ` Tom Rini
2019-02-28 21:23 Marek Vasut
2019-03-01 12:59 ` Tom Rini
2019-02-16 17:12 Marek Vasut
2019-02-18 14:29 ` Tom Rini
2018-12-10 4:53 Marek Vasut
2018-12-10 15:18 ` Tom Rini
2018-12-04 13:51 Marek Vasut
2018-12-05 3:12 ` Tom Rini
2018-12-03 19:08 Marek Vasut
2018-12-04 4:48 ` Tom Rini
2018-11-04 9:15 Marek Vasut
2018-11-05 12:23 ` Tom Rini
2018-10-19 10:29 Marek Vasut
2018-10-19 16:56 ` Tom Rini
2018-10-09 22:24 Marek Vasut
2018-10-11 14:10 ` Tom Rini
2018-10-05 21:27 Marek Vasut
2018-10-06 12:57 ` Tom Rini
2018-09-16 1:12 Marek Vasut
2018-09-17 12:03 ` Tom Rini
2018-08-30 14:11 Marek Vasut
2018-08-30 21:33 ` Tom Rini
2018-08-17 10:10 Marek Vasut
2018-08-17 13:56 ` Tom Rini
2018-07-26 7:35 Marek Vasut
2018-07-26 19:53 ` Tom Rini
2018-06-20 4:40 Marek Vasut
2018-06-21 18:21 ` Tom Rini
2018-06-17 0:02 Marek Vasut
2018-06-18 16:59 ` Tom Rini
2018-06-19 1:27 ` Marek Vasut
2018-06-13 4:05 Marek Vasut
2018-06-14 11:19 ` Tom Rini
2018-06-14 11:35 ` Marek Vasut
2018-06-14 13:07 ` Tom Rini
2018-06-14 20:58 ` Marek Vasut
2018-06-14 21:42 ` Tom Rini
2018-06-15 4:09 ` Marek Vasut
2018-06-15 11:46 ` Tom Rini
2018-06-18 14:24 ` Bin Meng
2018-06-01 23:07 Marek Vasut
2018-06-02 21:12 ` Tom Rini
2018-05-20 10:08 Marek Vasut
2018-05-21 1:59 ` Tom Rini
2018-05-02 23:49 Marek Vasut
2018-05-04 13:05 ` Tom Rini
2018-04-26 23:11 Marek Vasut
2018-04-27 11:20 ` Tom Rini
2018-04-22 3:29 Marek Vasut
2018-04-22 21:37 ` Tom Rini
2018-04-18 19:57 Marek Vasut
2018-04-19 3:14 ` Tom Rini
2018-04-20 13:46 ` Marek Vasut
2018-04-20 13:54 ` Tom Rini
2018-04-14 22:38 Marek Vasut
2018-04-15 17:52 ` Tom Rini
2018-04-14 9:20 Marek Vasut
2018-04-12 3:28 Marek Vasut
2018-04-12 3:55 ` Masahiro Yamada
2018-04-13 16:57 ` Tom Rini
2018-03-05 20:33 Marek Vasut
2018-03-06 1:28 ` Tom Rini
2018-03-01 17:34 Marek Vasut
2018-03-02 2:32 ` Tom Rini
2018-03-02 8:52 ` Marek Vasut
2018-02-23 16:58 Marek Vasut
2018-02-23 20:18 ` Tom Rini
2018-02-19 4:20 Marek Vasut
2018-02-20 4:00 ` Tom Rini
2018-02-17 21:02 Marek Vasut
2018-02-17 21:10 ` Tom Rini
2018-02-16 16:00 Marek Vasut
2018-02-17 20:52 ` 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=20190209124601.GD16814@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox