From: "Marek Behún" <marek.behun@nic.cz>
To: "Pali Rohár" <pali@kernel.org>
Cc: Stefan Roese <sr@denx.de>, u-boot@lists.denx.de
Subject: Re: [PATCH 4/5] arm: mvebu: turris_omnia: Add NVMe to boot targets
Date: Wed, 6 Apr 2022 21:32:33 +0200 [thread overview]
Message-ID: <20220406213233.460d104f@thinkpad> (raw)
In-Reply-To: <20220406093936.8854-4-pali@kernel.org>
On Wed, 6 Apr 2022 11:39:35 +0200
Pali Rohár <pali@kernel.org> wrote:
> U-Boot for Turris Omnia has already enabled NVMe support. So add NVMe to
> boot targets.
As in my previous message, an user may want to compile U-Boot without
NVMe support. They can do this now with menuconfig. If NVME support is
to be mandatory, it should be enforced in Kconfig.
But I don't think it should be mandatory.
Marek
next prev parent reply other threads:[~2022-04-06 19:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 9:39 [PATCH 1/5] arm: mvebu: turris_omnia: Fix RESET button message Pali Rohár
2022-04-06 9:39 ` [PATCH 2/5] arm: mvebu: turris_omnia: Define CONFIG_ETHPRIME instead of ethact= ENV Pali Rohár
2022-04-06 19:24 ` Marek Behún
2022-05-02 5:48 ` Stefan Roese
2022-05-02 15:41 ` Stefan Roese
2022-04-06 9:39 ` [PATCH 3/5] arm: mvebu: turris_omnia: Always enable MMC, SCSI and USB boot targets Pali Rohár
2022-04-06 19:31 ` Marek Behún
2022-04-08 9:00 ` Pali Rohár
2022-05-01 14:52 ` Pali Rohár
2022-05-01 18:53 ` Marek Behún
2022-05-02 15:42 ` Stefan Roese
2022-04-06 9:39 ` [PATCH 4/5] arm: mvebu: turris_omnia: Add NVMe to " Pali Rohár
2022-04-06 19:32 ` Marek Behún [this message]
2022-05-02 15:42 ` Stefan Roese
2022-04-06 9:39 ` [PATCH 5/5] arm: mvebu: turris_mox: Add NVMe and SCSI " Pali Rohár
2022-04-06 19:33 ` Marek Behún
2022-05-02 15:42 ` Stefan Roese
2022-04-06 19:23 ` [PATCH 1/5] arm: mvebu: turris_omnia: Fix RESET button message Marek Behún
2022-05-02 15:41 ` Stefan Roese
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=20220406213233.460d104f@thinkpad \
--to=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=sr@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.