ar71xx: fix WRT160NL and TP-Link partition parser patches
405-mtd-tp-link-partition-parser.patch was updating the WRT160NL's partition parser Kconfig. This patch moves the relevant change into the right file: 404-mtd-wrt160nl-trx-parser.patch Signed-off-by: Christian Lamparter <chunkeey@googlemail.com> SVN-Revision: 44662
This commit is contained in:
parent
0496393f9c
commit
9f16b370a0
@ -6,7 +6,7 @@
|
||||
|
||||
+config MTD_WRT160NL_PARTS
|
||||
+ tristate "Linksys WRT160NL partitioning support"
|
||||
+ depends on MTD_PARTITIONS && ATH79_MACH_WRT160NL
|
||||
+ depends on ATH79_MACH_WRT160NL
|
||||
+ ---help---
|
||||
+ Linksys WRT160NL partitioning support
|
||||
+
|
||||
|
@ -1,14 +1,5 @@
|
||||
--- a/drivers/mtd/Kconfig
|
||||
+++ b/drivers/mtd/Kconfig
|
||||
@@ -186,7 +186,7 @@ config MTD_BCM47XX_PARTS
|
||||
|
||||
config MTD_WRT160NL_PARTS
|
||||
tristate "Linksys WRT160NL partitioning support"
|
||||
- depends on MTD_PARTITIONS && ATH79_MACH_WRT160NL
|
||||
+ depends on ATH79_MACH_WRT160NL
|
||||
---help---
|
||||
Linksys WRT160NL partitioning support
|
||||
|
||||
@@ -206,6 +206,12 @@ config MTD_MYLOADER_PARTS
|
||||
You will still need the parsing functions to be called by the driver
|
||||
for your particular device. It won't happen automatically.
|
||||
|
@ -6,7 +6,7 @@
|
||||
|
||||
+config MTD_WRT160NL_PARTS
|
||||
+ tristate "Linksys WRT160NL partitioning support"
|
||||
+ depends on MTD_PARTITIONS && ATH79_MACH_WRT160NL
|
||||
+ depends on ATH79_MACH_WRT160NL
|
||||
+ ---help---
|
||||
+ Linksys WRT160NL partitioning support
|
||||
+
|
||||
|
@ -1,14 +1,5 @@
|
||||
--- a/drivers/mtd/Kconfig
|
||||
+++ b/drivers/mtd/Kconfig
|
||||
@@ -186,7 +186,7 @@ config MTD_BCM47XX_PARTS
|
||||
|
||||
config MTD_WRT160NL_PARTS
|
||||
tristate "Linksys WRT160NL partitioning support"
|
||||
- depends on MTD_PARTITIONS && ATH79_MACH_WRT160NL
|
||||
+ depends on ATH79_MACH_WRT160NL
|
||||
---help---
|
||||
Linksys WRT160NL partitioning support
|
||||
|
||||
@@ -206,6 +206,12 @@ config MTD_MYLOADER_PARTS
|
||||
You will still need the parsing functions to be called by the driver
|
||||
for your particular device. It won't happen automatically.
|
||||
|
Loading…
Reference in New Issue
Block a user