diff options
| author | Finn Thain <fthain@telegraphics.com.au> | 2019-01-15 05:18:56 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-01-22 10:21:43 +0100 |
| commit | 83d2aed4440c47acc813abeac4acf4390cb40a8c (patch) | |
| tree | 9ffc3c49936a255348ffcebfc9cb65427f8ffd11 /crypto/rmd128.c | |
| parent | misc: enclosure: Use struct_size() in kzalloc() (diff) | |
| download | linux-83d2aed4440c47acc813abeac4acf4390cb40a8c.tar.xz linux-83d2aed4440c47acc813abeac4acf4390cb40a8c.zip | |
scsi/atari_scsi: Don't select CONFIG_NVRAM
On powerpc, setting CONFIG_NVRAM=n builds a kernel with no NVRAM support.
Setting CONFIG_NVRAM=m enables the /dev/nvram misc device module without
enabling NVRAM support in drivers. Setting CONFIG_NVRAM=y enables the
misc device (built-in) and also enables NVRAM support in drivers.
m68k shares the valkyriefb driver with powerpc, and since that driver uses
NVRAM, it is affected by CONFIG_ATARI_SCSI, because of the use of
"select NVRAM". We can avoid the "select" here, but drivers still have
to interpret the CONFIG_NVRAM symbol consistently regardless of platform.
In this patch and the subsequent fbdev driver patch, the convention is
adopted across all relevant platforms whereby NVRAM functionality gets
enabled in a given device driver when the nvram misc device is built-in
or when both drivers are modules.
Acked-by: Michael Schmitz <schmitzmic@gmail.com>
Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto/rmd128.c')
0 files changed, 0 insertions, 0 deletions