From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: kah.jing.lee@intel.com, Dinh Nguyen <dinguyen@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@intel.com>
Subject: Re: [PATCH 2/2] arch: arm64: configs: Enable UBI and UBIFS
Date: Thu, 22 Jun 2023 11:23:15 +0200 [thread overview]
Message-ID: <0d1b3c55-4b11-9e63-e388-191d39d88df1@linaro.org> (raw)
In-Reply-To: <20230622085349.573942-1-kah.jing.lee@intel.com>
On 22/06/2023 10:53, kah.jing.lee@intel.com wrote:
> From: Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@intel.com>
>
> This patch is to enable UBI and UBIFS in Linux defconfig.
Why? Which board needs it? It's quite unusual to have this on arm64...
>
> Signed-off-by: Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@intel.com>
> Signed-off-by: Kah Jing Lee <kah.jing.lee@intel.com>
> ---
> arch/arm64/configs/defconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index a24609e14d50..23a6ebcb1a9e 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -470,6 +470,8 @@ CONFIG_IPMI_DEVICE_INTERFACE=m
> CONFIG_IPMI_SI=m
> CONFIG_HW_RANDOM=y
> CONFIG_HW_RANDOM_VIRTIO=y
> +CONFIG_MTD_UBI=y
> +CONFIG_UBIFS_FS=y
Not modules?
Are you sure you added the lines in appropriate place (matching
savedefconfig)?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-22 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 8:53 kah.jing.lee
2023-06-22 9:23 ` Krzysztof Kozlowski [this message]
2023-06-22 12:21 ` kah.jing.lee
2023-06-22 12:49 ` Krzysztof Kozlowski
2023-06-23 10:03 ` Lee, Kah Jing
2023-06-23 10:18 ` Krzysztof Kozlowski
2023-06-24 3:42 ` Lee, Kah Jing
2023-06-24 7:30 ` Krzysztof Kozlowski
2023-06-26 4:16 ` Lee, Kah Jing
2023-06-26 8:38 ` Krzysztof Kozlowski
2023-06-27 3:40 ` Lee, Kah Jing
2023-06-27 5:08 ` Dinh Nguyen
2023-07-03 4:06 ` Lee, Kah Jing
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=0d1b3c55-4b11-9e63-e388-191d39d88df1@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alif.zakuan.yuslaimi@intel.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=dinguyen@kernel.org \
--cc=kah.jing.lee@intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®