From: Quentin Schulz <quentin.schulz@cherry.de>
To: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Subject: Re: [PATCH 6/6] block: Remove "select BLK" from non-block drivers
Date: Tue, 14 Jan 2025 14:53:48 +0100 [thread overview]
Message-ID: <2b3e1050-7cbe-4dde-a298-5efb63cb4ebd@cherry.de> (raw)
In-Reply-To: <20241220222612.1757884-7-trini@konsulko.com>
Hi Tom,
On 12/20/24 11:22 PM, Tom Rini wrote:
> Now that block drivers are all selecting the BLK symbol, there's no need
> for other options to be select'ing BLK so that other required
> functionality can be enabled. Remove these places.
>
We have multiple commands depending on the BLK symbol.
BOOTSTD also depends on it, but I assume we should be able to network
boot without HW block drivers?
CMD_UFETCH wouldn't be usable without those drivers as well.
Should we do something about that by making them not depend on BLK e.g.
use CONFIG_IS_ENABLED in the right places? Not sure if all devicess
based on those archs have at least one HW block driver enabled. I guess
checking if all .config before and after that change are identical would
help us figure out if this could introduce a regression?
Cheers,
Quentin
next prev parent reply other threads:[~2025-01-14 13:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 22:22 [PATCH 0/6] Rework the BLK symbol usage in Kconfig Tom Rini
2024-12-20 22:22 ` [PATCH 1/6] drivers/mmc/Kconfig: Remove extraneous BLK dependencies Tom Rini
2024-12-22 23:49 ` Jaehoon Chung
2025-01-14 13:25 ` Quentin Schulz
2025-01-14 16:58 ` Tom Rini
2024-12-20 22:22 ` [PATCH 2/6] drivers/mmc/Kconfig: Make DM_MMC a hidden symbol Tom Rini
2024-12-23 18:26 ` Peter Robinson
2025-01-14 13:43 ` Quentin Schulz
2025-01-14 16:58 ` Tom Rini
2024-12-20 22:22 ` [PATCH 3/6] efi_loader: Depend on BLK Tom Rini
2024-12-20 22:50 ` Heinrich Schuchardt
2024-12-20 22:22 ` [PATCH 4/6] blk: Make block subsystems select BLK Tom Rini
2024-12-23 18:31 ` Peter Robinson
2024-12-23 18:53 ` Tom Rini
2025-01-14 13:45 ` Quentin Schulz
2025-01-14 16:58 ` Tom Rini
2025-01-15 17:38 ` Quentin Schulz
2024-12-20 22:22 ` [PATCH 5/6] mtd: Correct dependency of BLK Tom Rini
2024-12-23 18:27 ` Peter Robinson
2025-01-14 13:46 ` Quentin Schulz
2024-12-20 22:22 ` [PATCH 6/6] block: Remove "select BLK" from non-block drivers Tom Rini
2024-12-23 18:26 ` Peter Robinson
2025-01-14 13:53 ` Quentin Schulz [this message]
2025-01-14 16:59 ` Tom Rini
2025-01-15 17:49 ` Quentin Schulz
2025-01-15 20:20 ` Tom Rini
2025-01-16 9:21 ` Quentin Schulz
2025-01-16 14:33 ` Tom Rini
2025-01-15 1:22 ` [PATCHv2 0/6] Rework the BLK symbol usage in Kconfig Tom Rini
2025-01-15 1:22 ` [PATCHv2 1/6] drivers/mmc/Kconfig: Remove extraneous BLK dependencies Tom Rini
2025-01-15 1:22 ` [PATCHv2 2/6] drivers/mmc/Kconfig: Make DM_MMC a hidden symbol Tom Rini
2025-01-15 1:22 ` [PATCHv2 3/6] efi_loader: Depend on BLK Tom Rini
2025-01-15 1:22 ` [PATCHv2 4/6] blk: Make block subsystems select BLK Tom Rini
2025-01-15 17:51 ` Quentin Schulz
2025-01-15 18:28 ` Tom Rini
2025-01-15 1:22 ` [PATCHv2 5/6] mtd: Correct dependency of BLK Tom Rini
2025-01-15 1:22 ` [PATCHv2 6/6] block: Remove "select BLK" from non-block drivers Tom Rini
2025-01-21 4:49 ` [PATCHv2 0/6] Rework the BLK symbol usage in Kconfig 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=2b3e1050-7cbe-4dde-a298-5efb63cb4ebd@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=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