forked from ~ljy/RK356X_SDK_RELEASE

hc
2024-05-14 bedbef8ad3e75a304af6361af235302bcc61d06b
kernel/drivers/memstick/core/Kconfig
....@@ -1,3 +1,4 @@
1
+# SPDX-License-Identifier: GPL-2.0-only
12 #
23 # MemoryStick core configuration
34 #
....@@ -5,16 +6,16 @@
56 comment "MemoryStick drivers"
67
78 config MEMSTICK_UNSAFE_RESUME
8
- bool "Allow unsafe resume (DANGEROUS)"
9
- help
10
- If you say Y here, the MemoryStick layer will assume that all
11
- cards stayed in their respective slots during the suspend. The
12
- normal behaviour is to remove them at suspend and
13
- redetecting them at resume. Breaking this assumption will
14
- in most cases result in data corruption.
9
+ bool "Allow unsafe resume (DANGEROUS)"
10
+ help
11
+ If you say Y here, the MemoryStick layer will assume that all
12
+ cards stayed in their respective slots during the suspend. The
13
+ normal behaviour is to remove them at suspend and
14
+ redetecting them at resume. Breaking this assumption will
15
+ in most cases result in data corruption.
1516
16
- This option is usually just for embedded systems which use
17
- a MemoryStick card for rootfs. Most people should say N here.
17
+ This option is usually just for embedded systems which use
18
+ a MemoryStick card for rootfs. Most people should say N here.
1819
1920 config MSPRO_BLOCK
2021 tristate "MemoryStick Pro block device driver"