From: Joe Perches <joe@perches.com>
To: Alexander Sverdlin <alexander.sverdlin@nokia.com>,
David Daney <david.daney@cavium.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: octeon: Remove vestiges of CONFIG_CAVIUM_RESERVE32
Date: Fri, 22 Jul 2022 00:53:15 -0700 [thread overview]
Message-ID: <bf9c7aaae2ca014b6efde5b75015eea592519348.camel@perches.com> (raw)
In-Reply-To: <6878a4d0-a12d-ae8c-f5b1-08147203cd7d@nokia.com>
On Thu, 2022-07-21 at 14:19 +0200, Alexander Sverdlin wrote:
> Hello Joe!
>
> On 13/07/2021 19:49, Joe Perches wrote:
> > The config option CAVIUM_RESERVE32 is not used.
>
> We use it. Does it make sense that I submit a revert and a patch adding the option to Kconfig?
yes.
prev parent reply other threads:[~2022-07-22 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 17:49 [PATCH] MIPS: octeon: Remove vestiges of CONFIG_CAVIUM_RESERVE32 Joe Perches
2021-07-19 11:27 ` Thomas Bogendoerfer
2022-07-21 12:19 ` Alexander Sverdlin
2022-07-22 7:53 ` Joe Perches [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=bf9c7aaae2ca014b6efde5b75015eea592519348.camel@perches.com \
--to=joe@perches.com \
--cc=alexander.sverdlin@nokia.com \
--cc=david.daney@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).