From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alexander A Sverdlin <alexander.sverdlin@nokia.com>
Cc: linux-mips@vger.kernel.org, Joe Perches <joe@perches.com>,
Corey Minyard <cminyard@mvista.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] MIPS: Restore CONFIG_CAVIUM_RESERVE32
Date: Sat, 30 Jul 2022 11:02:35 +0200 [thread overview]
Message-ID: <20220730090235.GA4620@alpha.franken.de> (raw)
In-Reply-To: <20220725091740.28188-1-alexander.sverdlin@nokia.com>
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 ]
prev parent reply other threads:[~2022-07-30 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 9:17 [PATCH 0/2] MIPS: Restore CONFIG_CAVIUM_RESERVE32 Alexander A Sverdlin
2022-07-25 9:17 ` [PATCH 1/2] MIPS: Introduce CAVIUM_RESERVE32 Kconfig option Alexander A Sverdlin
2022-08-30 3:02 ` Yu Zhao
2022-09-05 18:50 ` Yu Zhao
2022-09-06 7:55 ` Alexander Sverdlin
2022-07-25 9:17 ` [PATCH 2/2] Revert "MIPS: octeon: Remove vestiges of CONFIG_CAVIUM_RESERVE32" Alexander A Sverdlin
2022-07-30 17:18 ` Joe Perches
2022-07-30 9:02 ` Thomas Bogendoerfer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220730090235.GA4620@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alexander.sverdlin@nokia.com \
--cc=cminyard@mvista.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).