[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a09de6e0-700b-0715-06a8-150ab41e8e7f@acm.org>
Date: Wed, 27 Jul 2022 10:46:03 -0700
From: Bart Van Assche <bvanassche@....org>
To: Chetan C R <quic_cchinnad@...cinc.com>, jejb@...ux.ibm.com
Cc: linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH V1] scsi: ufs: Get boot device storage type from command
line
On 7/27/22 01:28, Chetan C R wrote:
> diff --git a/drivers/ufs/Kconfig b/drivers/ufs/Kconfig
> index 90226f7..9d2f84e 100644
> --- a/drivers/ufs/Kconfig
> +++ b/drivers/ufs/Kconfig
> @@ -9,6 +9,7 @@ menuconfig SCSI_UFSHCD
> select PM_DEVFREQ
> select DEVFREQ_GOV_SIMPLE_ONDEMAND
> select NLS
> + select UFS_QCOM_CMDLINE if ARCH_QCOM
> help
> Enables support for UFS (Universal Flash Storage) host controllers.
> A UFS host controller is an electronic component that is able to
[ ... ]
> +__setup("androidboot.bootdevice=", get_android_boot_dev_v3);
How can this work since __setup() declarations should occur in the core
kernel and since the ufshcd driver can be built as a kernel module?
Thanks,
Bart.
Powered by blists - more mailing lists