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>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
Wolfgang Denk <wd@denx.de>
Subject: Re: [PATCH 1/5] disk: Add an option for partitions in SPL
Date: Mon, 14 Mar 2022 08:49:44 -0400 [thread overview]
Message-ID: <20220314124944.GD9986@bill-the-cat> (raw)
In-Reply-To: <20220311191005.364540-2-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
On Fri, Mar 11, 2022 at 12:10:01PM -0700, Simon Glass wrote:
> In some cases we do not want to enable partition support in SPL. Add an
> option to allow this.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> disk/Kconfig | 24 ++++++++++++++++++++----
> disk/Makefile | 6 +++---
> drivers/block/blk-uclass.c | 2 +-
> 3 files changed, 24 insertions(+), 8 deletions(-)
I'm not sure this makes sense? I thought when I looked in to this last
the only place where we had partition code being linked and not
discarded in the case of SPL and no devices that would have partitions
on them was one xilinx platform. How do we get to bringing in partition
code and not having something that uses it?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-03-14 12:49 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 [this message]
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
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=20220314124944.GD9986@bill-the-cat \
--to=trini@konsulko.com \
--cc=patrick.delaunay@foss.st.com \
--cc=sjg@chromium.org \
--cc=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=wd@denx.de \
--cc=xypron.glpk@gmx.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