mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Paul Mackerras <paulus@samba.org>, Scott Wood <oss@buserror.net>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/85xx: Remove FSL_85XX_CACHE_SRAM
Date: Mon, 4 Apr 2022 16:26:00 -0500	[thread overview]
Message-ID: <YktiaO4n62O7BqXZ@robh.at.kernel.org> (raw)
In-Reply-To: <9949813a6b758903b7bee910f798ba2ca82ff8ee.1648720908.git.christophe.leroy@csgroup.eu>

On Thu, 31 Mar 2022 12:03:06 +0200, Christophe Leroy wrote:
> CONFIG_FSL_85XX_CACHE_SRAM is an option that is not
> user selectable and which is not selected by any driver
> nor any defconfig.
> 
> Remove it and all associated code.
> 
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
>  .../bindings/powerpc/fsl/cache_sram.txt       |  20 --
>  .../powerpc/include/asm/fsl_85xx_cache_sram.h |  35 ---
>  arch/powerpc/platforms/85xx/Kconfig           |   9 -
>  arch/powerpc/sysdev/Makefile                  |   1 -
>  arch/powerpc/sysdev/fsl_85xx_cache_ctlr.h     |  88 -------
>  arch/powerpc/sysdev/fsl_85xx_cache_sram.c     | 147 ------------
>  arch/powerpc/sysdev/fsl_85xx_l2ctlr.c         | 216 ------------------
>  7 files changed, 516 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/powerpc/fsl/cache_sram.txt
>  delete mode 100644 arch/powerpc/include/asm/fsl_85xx_cache_sram.h
>  delete mode 100644 arch/powerpc/sysdev/fsl_85xx_cache_ctlr.h
>  delete mode 100644 arch/powerpc/sysdev/fsl_85xx_cache_sram.c
>  delete mode 100644 arch/powerpc/sysdev/fsl_85xx_l2ctlr.c
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-04-04 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 10:03 Christophe Leroy
2022-04-04 21:26 ` Rob Herring [this message]
2022-05-24 11:09 ` Michael Ellerman

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=YktiaO4n62O7BqXZ@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=oss@buserror.net \
    --cc=paulus@samba.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

all inboxes | Powered by JetHome®