MIPS: Restore CONFIG_CAVIUM_RESERVE32

[PATCH 0/2] MIPS: Restore CONFIG_CAVIUM_RESERVE32

Alexander A Sverdlin posted 2 patches 3 years, 8 months ago

Download series mbox

arch/mips/cavium-octeon/Kconfig                    | 12 +++++++
arch/mips/cavium-octeon/executive/cvmx-cmd-queue.c | 21 +++++++++---
arch/mips/cavium-octeon/setup.c                    | 38 +++++++++++++++++++++-
3 files changed, 66 insertions(+), 5 deletions(-)

Expand all Fold all

[PATCH 0/2] MIPS: Restore CONFIG_CAVIUM_RESERVE32

Posted by Alexander A Sverdlin 3 years, 8 months ago

From: Alexander Sverdlin <alexander.sverdlin@nokia.com>

We have been using the option but the definition in the Kconfig has not
been upstreamed. Fix that.

Alexander Sverdlin (2):
  MIPS: Introduce CAVIUM_RESERVE32 Kconfig option
  Revert "MIPS: octeon: Remove vestiges of CONFIG_CAVIUM_RESERVE32"

 arch/mips/cavium-octeon/Kconfig                    | 12 +++++++
 arch/mips/cavium-octeon/executive/cvmx-cmd-queue.c | 21 +++++++++---
 arch/mips/cavium-octeon/setup.c                    | 38 +++++++++++++++++++++-
 3 files changed, 66 insertions(+), 5 deletions(-)

-- 
2.10.2

Re: [PATCH 0/2] MIPS: Restore CONFIG_CAVIUM_RESERVE32

Posted by Thomas Bogendoerfer 3 years, 8 months ago

On Mon, Jul 25, 2022 at 11:17:38AM +0200, Alexander A Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@nokia.com>
> 
> We have been using the option but the definition in the Kconfig has not
> been upstreamed. Fix that.
> 
> Alexander Sverdlin (2):
>   MIPS: Introduce CAVIUM_RESERVE32 Kconfig option
>   Revert "MIPS: octeon: Remove vestiges of CONFIG_CAVIUM_RESERVE32"
> 
>  arch/mips/cavium-octeon/Kconfig                    | 12 +++++++
>  arch/mips/cavium-octeon/executive/cvmx-cmd-queue.c | 21 +++++++++---
>  arch/mips/cavium-octeon/setup.c                    | 38 +++++++++++++++++++++-
>  3 files changed, 66 insertions(+), 5 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]