From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Soeren Moch <smoch@web.de>,
q@bill-the-cat
Subject: Re: [PATCH 2/5] tbs2910: Disable ext4 write
Date: Fri, 11 Mar 2022 23:04:08 -0500 [thread overview]
Message-ID: <20220312040408.GY5020@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ34E1TA5C0yzs-p4adJ497HQu3CU7a9hrnUT23Yj-qM2w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Fri, Mar 11, 2022 at 07:24:41PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Fri, 11 Mar 2022 at 12:58, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Fri, Mar 11, 2022 at 12:10:02PM -0700, Simon Glass wrote:
> >
> > > This board is right up against the size limit. Drop ext4 writing to give
> > > it some more space.
> > >
> > > Signed-off-by: Simon Glass <sjg@chromium.org>
> >
> > I would really like to see what LTO does here instead of removing
> > functionality. I'm sure it shrinks things enough to fit, but it does
> > need run time testing.
>
> Well let's see if the maintainer responds. But this is blocking the
> EFI series which we really need to get in it. It can always be cleaned
> up later.
Erm, Soeren has been quite responsive.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-03-12 4:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 19:10 [PATCH 0/5] Reduce size of a few boards Simon Glass
2022-03-11 19:10 ` [PATCH 1/5] disk: Add an option for partitions in SPL Simon Glass
2022-03-14 12:49 ` Tom Rini
2022-03-14 18:24 ` Simon Glass
2022-03-14 18:31 ` Tom Rini
2022-03-14 19:21 ` Simon Glass
2022-03-14 19:38 ` Tom Rini
2022-03-26 2:46 ` Tom Rini
2022-04-14 8:30 ` AKASHI Takahiro
2022-03-11 19:10 ` [PATCH 2/5] tbs2910: Disable ext4 write Simon Glass
2022-03-11 19:58 ` Tom Rini
2022-03-12 2:24 ` Simon Glass
2022-03-12 4:04 ` Tom Rini [this message]
2022-03-12 5:02 ` Simon Glass
2022-03-11 22:57 ` Soeren Moch
2022-03-12 4:45 ` Simon Glass
2022-03-11 19:10 ` [PATCH 3/5] rcar3_salvator-x: Drop EFI_LOADER Simon Glass
2022-03-11 20:21 ` Tom Rini
2022-03-12 2:24 ` Simon Glass
2022-03-14 12:54 ` Tom Rini
2022-03-14 18:24 ` Simon Glass
2022-03-11 19:10 ` [PATCH 4/5] phycore-rk3288: Avoid enabling partition support in SPL Simon Glass
2022-04-20 12:22 ` Kever Yang
2022-03-11 19:10 ` [PATCH 5/5] disk: Use a helper function to reduce duplication Simon Glass
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=20220312040408.GY5020@bill-the-cat \
--to=trini@konsulko.com \
--cc=q@bill-the-cat \
--cc=sjg@chromium.org \
--cc=smoch@web.de \
--cc=takahiro.akashi@linaro.org \
--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