diff mbox

[OpenWrt-Devel,1/4] ar71xx: fix WRT160NL and TP-Link partition parser patches

Message ID 2109893.ODUENLQ88s@debian64
State Accepted
Headers show

Commit Message

Christian Lamparter March 6, 2015, 6:46 p.m. UTC
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>
---
 .../linux/ar71xx/patches-3.14/404-mtd-wrt160nl-trx-parser.patch  | 2 +-
 .../ar71xx/patches-3.14/405-mtd-tp-link-partition-parser.patch   | 9 ---------
 .../linux/ar71xx/patches-3.18/404-mtd-wrt160nl-trx-parser.patch  | 2 +-
 .../ar71xx/patches-3.18/405-mtd-tp-link-partition-parser.patch   | 9 ---------
 4 files changed, 2 insertions(+), 20 deletions(-)

Comments

Christian Lamparter March 11, 2015, 1:14 p.m. UTC | #1
On Fri, Mar 6, 2015 at 7:46 PM, Christian Lamparter
<chunkeey@googlemail.com> wrote:
> 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>
> ---
Ping?

Please apply [this series], or tell me what's wrong/needs to be done.

Thanks,
Christian
diff mbox

Patch

diff --git a/target/linux/ar71xx/patches-3.14/404-mtd-wrt160nl-trx-parser.patch b/target/linux/ar71xx/patches-3.14/404-mtd-wrt160nl-trx-parser.patch
index e49d72e..b5f4b52 100644
--- a/target/linux/ar71xx/patches-3.14/404-mtd-wrt160nl-trx-parser.patch
+++ b/target/linux/ar71xx/patches-3.14/404-mtd-wrt160nl-trx-parser.patch
@@ -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
 +
diff --git a/target/linux/ar71xx/patches-3.14/405-mtd-tp-link-partition-parser.patch b/target/linux/ar71xx/patches-3.14/405-mtd-tp-link-partition-parser.patch
index 0688bb8..74e79ea 100644
--- a/target/linux/ar71xx/patches-3.14/405-mtd-tp-link-partition-parser.patch
+++ b/target/linux/ar71xx/patches-3.14/405-mtd-tp-link-partition-parser.patch
@@ -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.
diff --git a/target/linux/ar71xx/patches-3.18/404-mtd-wrt160nl-trx-parser.patch b/target/linux/ar71xx/patches-3.18/404-mtd-wrt160nl-trx-parser.patch
index e49d72e..b5f4b52 100644
--- a/target/linux/ar71xx/patches-3.18/404-mtd-wrt160nl-trx-parser.patch
+++ b/target/linux/ar71xx/patches-3.18/404-mtd-wrt160nl-trx-parser.patch
@@ -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
 +
diff --git a/target/linux/ar71xx/patches-3.18/405-mtd-tp-link-partition-parser.patch b/target/linux/ar71xx/patches-3.18/405-mtd-tp-link-partition-parser.patch
index 0688bb8..74e79ea 100644
--- a/target/linux/ar71xx/patches-3.18/405-mtd-tp-link-partition-parser.patch
+++ b/target/linux/ar71xx/patches-3.18/405-mtd-tp-link-partition-parser.patch
@@ -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.