From: Scott Wood <oss@buserror.net>
To: wangwenhu <wenhu.pku@gmail.com>,
Kumar Gala <galak@kernel.crashing.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Rai Harninder <harninder.rai@nxp.com>,
wenhu.wang@vivo.com, trivial@kernel.org
Subject: Re: [PATCH] powerpc/Kconfig: Make FSL_85XX_CACHE_SRAM configurable
Date: Mon, 20 Jan 2020 21:25:25 -0600 [thread overview]
Message-ID: <bd0fa23b900fe967a8c3c11abd1ba9a47cec474f.camel@buserror.net> (raw)
In-Reply-To: <20200120144327.20800-1-wenhu.pku@gmail.com>
On Mon, 2020-01-20 at 06:43 -0800, wangwenhu wrote:
> From: wangwenhu <wenhu.wang@vivo.com>
>
> When generating .config file with menuconfig on Freescale BOOKE
> SOC, FSL_85XX_CACHE_SRAM is not configurable for the lack of
> description in the Kconfig field, which makes it impossible
> to support L2Cache-Sram driver. Add a description to make it
> configurable.
>
> Signed-off-by: wangwenhu <wenhu.wang@vivo.com>
The intent was that drivers using the SRAM API would select the symbol. What
is the use case for selecting it manually?
Since this code was added almost ten years ago and there are still no (in-
tree?) users of the API, we should just remove the sram code (unless this
prods someone to submit such a user very soon).
-Scott
next prev parent reply other threads:[~2020-01-21 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 14:43 [PATCH] powerpc/Kconfig: Make FSL_85XX_CACHE_SRAM configurable wangwenhu
2020-01-21 3:25 ` Scott Wood [this message]
2020-01-21 5:20 ` 王文虎
2020-01-21 5:49 ` [PATCH] " Scott Wood
2020-01-21 6:38 ` 王文虎
2020-02-29 23:12 ` Scott Wood
2020-03-02 4:42 ` 王文虎
2020-03-02 8:58 ` Scott Wood
2020-03-02 9:51 ` 王文虎
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=bd0fa23b900fe967a8c3c11abd1ba9a47cec474f.camel@buserror.net \
--to=oss@buserror.net \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=harninder.rai@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=trivial@kernel.org \
--cc=wenhu.pku@gmail.com \
--cc=wenhu.wang@vivo.com \
/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).