Discussion:
[Patch v3] 2/7] ata: Remove ARCH_KIRKWOOD dependency
Andrew Lunn
2014-08-30 16:46:07 UTC
Permalink
mach-kirkwood has been removed, now that kirkwood lives in mach-mvebu.
ARCH_MVEBU is sufficient.

Signed-off-by: Andrew Lunn <***@lunn.ch>
Cc: Tejun Heo <***@kernel.org>
Cc: linux-***@vger.kernel.org
---
drivers/ata/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
index e1b92788c225..cd4cccbfd2ab 100644
--- a/drivers/ata/Kconfig
+++ b/drivers/ata/Kconfig
@@ -299,7 +299,7 @@ config SATA_HIGHBANK

config SATA_MV
tristate "Marvell SATA support"
- depends on PCI || ARCH_DOVE || ARCH_KIRKWOOD || ARCH_MV78XX0 || \
+ depends on PCI || ARCH_DOVE || ARCH_MV78XX0 || \
ARCH_MVEBU || ARCH_ORION5X || COMPILE_TEST
select GENERIC_PHY
help
--
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Tejun Heo
2014-08-31 11:02:46 UTC
Permalink
Post by Andrew Lunn
mach-kirkwood has been removed, now that kirkwood lives in mach-mvebu.
ARCH_MVEBU is sufficient.
Acked-by: Tejun Heo <***@kernel.org>

Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Rafael J. Wysocki
2014-09-01 13:56:43 UTC
Permalink
This is mostly a resend of these patches, removing mach-kirkwood. Not
all maintainers picked up there patches, which has resulted in some
dead kernel configuration in v3.17-rcX.
The patch set has been rebased on v3.17-rc2, and it is intended that
Jason Cooper will submit them for inclusion in an RC. Subsystem
maintainers do not need to do anything.
The last patch "cpufreq: Remove ARCH_KIRKWOOD dependency" is new,
since what it is removing was added during v3.16-rcX. It follows the
pattern of all the other patches.
cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency
ata: Remove ARCH_KIRKWOOD dependency
thermal: Remove ARCH_KIRKWOOD dependency
leds: Remove ARCH_KIRKWOOD dependency
rtc: Remove ARCH_KIRKWOOD dependency
watchdog: Remove ARCH_KIRKWOOD dependency
cpufreq: Remove ARCH_KIRKWOOD dependency
I have no problems with these changes, but what exactly am I supposed to do?

Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-pm" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Andrew Lunn
2014-09-01 14:03:20 UTC
Permalink
Post by Rafael J. Wysocki
This is mostly a resend of these patches, removing mach-kirkwood. Not
all maintainers picked up there patches, which has resulted in some
dead kernel configuration in v3.17-rcX.
The patch set has been rebased on v3.17-rc2, and it is intended that
Jason Cooper will submit them for inclusion in an RC. Subsystem
maintainers do not need to do anything.
The last patch "cpufreq: Remove ARCH_KIRKWOOD dependency" is new,
since what it is removing was added during v3.16-rcX. It follows the
pattern of all the other patches.
cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency
ata: Remove ARCH_KIRKWOOD dependency
thermal: Remove ARCH_KIRKWOOD dependency
leds: Remove ARCH_KIRKWOOD dependency
rtc: Remove ARCH_KIRKWOOD dependency
watchdog: Remove ARCH_KIRKWOOD dependency
cpufreq: Remove ARCH_KIRKWOOD dependency
I have no problems with these changes, but what exactly am I supposed to do?
Jason will submit the whole series. So an Acked-by: would be nice.

Andrew
Rafael J. Wysocki
2014-09-01 23:46:36 UTC
Permalink
Post by Andrew Lunn
Post by Rafael J. Wysocki
This is mostly a resend of these patches, removing mach-kirkwood. Not
all maintainers picked up there patches, which has resulted in some
dead kernel configuration in v3.17-rcX.
The patch set has been rebased on v3.17-rc2, and it is intended that
Jason Cooper will submit them for inclusion in an RC. Subsystem
maintainers do not need to do anything.
The last patch "cpufreq: Remove ARCH_KIRKWOOD dependency" is new,
since what it is removing was added during v3.16-rcX. It follows the
pattern of all the other patches.
cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency
ata: Remove ARCH_KIRKWOOD dependency
thermal: Remove ARCH_KIRKWOOD dependency
leds: Remove ARCH_KIRKWOOD dependency
rtc: Remove ARCH_KIRKWOOD dependency
watchdog: Remove ARCH_KIRKWOOD dependency
cpufreq: Remove ARCH_KIRKWOOD dependency
I have no problems with these changes, but what exactly am I supposed to do?
Jason will submit the whole series. So an Acked-by: would be nice.
OK, so please regard the cpuidle and cpufreq patches as ACKed.

Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-pm" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Jason Cooper
2014-09-09 15:10:22 UTC
Permalink
Andrew,
This is mostly a resend of these patches, removing mach-kirkwood. Not
all maintainers picked up there patches, which has resulted in some
dead kernel configuration in v3.17-rcX.
The patch set has been rebased on v3.17-rc2, and it is intended that
Jason Cooper will submit them for inclusion in an RC. Subsystem
maintainers do not need to do anything.
The last patch "cpufreq: Remove ARCH_KIRKWOOD dependency" is new,
since what it is removing was added during v3.16-rcX. It follows the
pattern of all the other patches.
cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency
ata: Remove ARCH_KIRKWOOD dependency
thermal: Remove ARCH_KIRKWOOD dependency
leds: Remove ARCH_KIRKWOOD dependency
rtc: Remove ARCH_KIRKWOOD dependency
watchdog: Remove ARCH_KIRKWOOD dependency
cpufreq: Remove ARCH_KIRKWOOD dependency
drivers/ata/Kconfig | 2 +-
drivers/cpufreq/Kconfig.arm | 2 +-
drivers/cpuidle/Kconfig.arm | 2 +-
drivers/leds/Kconfig | 4 ++--
drivers/rtc/Kconfig | 2 +-
drivers/thermal/Kconfig | 2 +-
drivers/watchdog/Kconfig | 2 +-
7 files changed, 8 insertions(+), 8 deletions(-)
Applied to mvebu/fixes for v3.17 with all the various Acks. Also,
please don't add the extra ']' in the Subject lines, 'git am' threw a
gasket on that so I had to manually edit before applying. Not a big
deal, just an fyi.

thx,

Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-pm" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Loading...