From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/3] mtd: nand: trim down NAND layer a bit
Date: Tue, 18 Jun 2024 08:13:45 +0200 [thread overview]
Message-ID: <171869122549.3822978.7856249240200139957.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240614133603.2452891-1-s.hauer@pengutronix.de>
On Fri, 14 Jun 2024 15:36:00 +0200, Sascha Hauer wrote:
> The NAND layer has become bigger with the last update causing size
> constrained configs like am335x_mlo_defconfig to fail because the binary
> gets too big. Squeeze some bytes out of the binary space for such
> configs by disabling some unneeded features.
>
> Sascha Hauer (3):
> mtd: nand: Kconfig: whitespace cleanups
> mtd: nand: make exec_op optional
> mtd: nand: make interleaved placement optional
>
> [...]
Applied, thanks!
[1/3] mtd: nand: Kconfig: whitespace cleanups
https://git.pengutronix.de/cgit/barebox/commit/?id=eb6429a2b87b (link may not be stable)
[2/3] mtd: nand: make exec_op optional
https://git.pengutronix.de/cgit/barebox/commit/?id=0958c15cebd7 (link may not be stable)
[3/3] mtd: nand: make interleaved placement optional
https://git.pengutronix.de/cgit/barebox/commit/?id=d1fe68f1b010 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-06-18 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 13:36 Sascha Hauer
2024-06-14 13:36 ` [PATCH 1/3] mtd: nand: Kconfig: whitespace cleanups Sascha Hauer
2024-06-14 13:36 ` [PATCH 2/3] mtd: nand: make exec_op optional Sascha Hauer
2024-06-14 13:36 ` [PATCH 3/3] mtd: nand: make interleaved placement optional Sascha Hauer
2024-06-18 6:13 ` Sascha Hauer [this message]
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=171869122549.3822978.7856249240200139957.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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