From: Olof Johansson <olof@lixom.net>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: liwei213@huawei.com, john.stultz@linaro.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, marc.w.gonzalez@free.fr
Subject: Re: [PATCH] arm64: defconfig: Update UFSHCD for Hi3660 soc
Date: Sun, 28 Apr 2019 23:19:42 -0700 [thread overview]
Message-ID: <20190429061942.2e3xy3ki7ua5woai@localhost> (raw)
In-Reply-To: <20190416170221.13764-1-valentin.schneider@arm.com>
On Tue, Apr 16, 2019 at 06:02:21PM +0100, Valentin Schneider wrote:
> Commit 7ee7ef24d02d ("scsi: arm64: defconfig: enable configs for Hisilicon ufs")
> set 'CONFIG_SCSI_UFS_HISI=y', but the configs it depends
> on
>
> (CONFIG_SCSI_HFSHCD_PLATFORM && CONFIG_SCSI_UFSHCD)
>
> were left to being built as modules.
>
> Commit 1f4fa50dd48f ("arm64: defconfig: Regenerate for v4.20") "fixed"
> that by reverting to 'CONFIG_SCSI_UFS_HISI=m'.
>
> Thing is, if the rootfs is stored in the on-board flash (which
> is the "canonical" way of doing things), we either need these drivers
> to be built-in, or we need to fiddle with an initramfs to access that
> flash and eventually load the modules installed over there.
>
> The former is the easiest, do that.
>
> Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
Applied, thanks!
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-04-29 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 17:02 [PATCH] arm64: defconfig: Update UFSHCD for Hi3660 soc Valentin Schneider
2019-04-17 0:25 ` Leo Yan
2019-04-17 8:03 ` Marc Gonzalez
2019-04-17 10:09 ` Valentin Schneider
2019-04-29 6:19 ` Olof Johansson
2019-04-29 6:19 ` Olof Johansson [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=20190429061942.2e3xy3ki7ua5woai@localhost \
--to=olof@lixom.net \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei213@huawei.com \
--cc=marc.w.gonzalez@free.fr \
--cc=valentin.schneider@arm.com \
/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