diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2015-01-20 07:36:53 +0100 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2015-01-20 08:06:58 +0100 |
| commit | a85cade6762bf566698e625ec1a4461245e40768 (patch) | |
| tree | e6dc30c400417d313c2546aa0bc93ca1905608b5 /arch/powerpc/configs/pasemi_defconfig | |
| parent | powerpc/kvm: Create proper names for the kvm_host_state PMU fields (diff) | |
| download | linux-a85cade6762bf566698e625ec1a4461245e40768.tar.xz linux-a85cade6762bf566698e625ec1a4461245e40768.zip | |
powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/powerpc/configs/pasemi_defconfig')
| -rw-r--r-- | arch/powerpc/configs/pasemi_defconfig | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/arch/powerpc/configs/pasemi_defconfig b/arch/powerpc/configs/pasemi_defconfig index 3e72c8c06a0d..8f94782eb907 100644 --- a/arch/powerpc/configs/pasemi_defconfig +++ b/arch/powerpc/configs/pasemi_defconfig @@ -54,7 +54,6 @@ CONFIG_MTD_SLRAM=y CONFIG_MTD_PHRAM=y CONFIG_MTD_NAND=y CONFIG_MTD_NAND_PASEMI=y -CONFIG_PROC_DEVICETREE=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=16384 @@ -69,7 +68,6 @@ CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=y CONFIG_CHR_DEV_SCH=y -CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y CONFIG_ATA=y @@ -134,7 +132,6 @@ CONFIG_HID_NTRIG=y CONFIG_HID_PANTHERLORD=y CONFIG_HID_PETALYNX=y CONFIG_HID_SAMSUNG=y -CONFIG_HID_SONY=y CONFIG_HID_SUNPLUS=y CONFIG_HID_GREENASIA=y CONFIG_HID_SMARTJOYPLUS=y |