mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: Julian Braha <julianbraha@gmail.com>,
	maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
	chleroy@kernel.org, Frank.Li@kernel.org, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, kernel-janitors@vger.kernel.org,
	linusw@kernel.org, kees@kernel.org, colin.i.king@gmail.com,
	rosenp@gmail.com, joao@joaoff.com, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH v3] powerpc: remove dead 440SP code
Date: Mon, 5 Oct 2026 15:40:36 +0200	[thread overview]
Message-ID: <asOo1HzrYIysrWF_@parshuram> (raw)
In-Reply-To: <ar7J3nl2pNW-B7AO@lizhi-Precision-Tower-5810>

On 01-10-26, 17:00, Frank Li wrote:
> On Tue, Sep 01, 2026 at 04:23:41PM +0100, Julian Braha wrote:
> > The 440SP config option can never be enabled, making all references to it
> > dead code.
> >
> > The only board using CONFIG_440SP was IBM LUAN, which was commented out by
> > commit f65573314e4e ("[POWERPC] Re-organize Kconfig code for 4xx in
> > arch/powerpc") then removed by commit ff5f483f3091 ("powerpc: 4xx: remove
> > commented out Kconfig entries").
> >
> > Let's remove support for 440SP, since nobody can be using it anyway.
> >
> > This dead code was found by kconfirm, a static analysis tool for Kconfig.

> >
> > Signed-off-by: Julian Braha <julianbraha@gmail.com>
> > ---
> 
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> 
> > Changes since v2:
> > - cleaned up preprocessor condition
> >
> > Link to v2:
> > https://lore.kernel.org/all/20260901150645.1199097-1-julianbraha@gmail.com/
> >
> > Changes since v1:
> > - added historic details to description
> >
> > Link to v1:
> > https://lore.kernel.org/all/20260816125615.985387-1-julianbraha@gmail.com/
> > ---
> >  arch/powerpc/boot/cuboot-katmai.c   |  2 +-
> >  arch/powerpc/include/asm/async_tx.h |  2 +-
> >  arch/powerpc/include/asm/dcr-regs.h | 10 +++++-----
> >  arch/powerpc/kernel/cpu_specs_44x.h | 12 ------------
> >  arch/powerpc/platforms/44x/Kconfig  |  3 ---
> >  drivers/dma/Kconfig                 |  2 +-
> >  drivers/dma/ppc4xx/adma.c           |  9 ---------
> >  drivers/dma/ppc4xx/adma.h           |  2 +-
> >  drivers/dma/ppc4xx/dma.h            |  9 ---------

Can you send dmaengine only parts please.. or if this goes thru ppc
tree:

Acked-by: Vinod Koul <vkoul@kernel.org>

-- 
~Vinod

      reply	other threads:[~2026-10-05 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 15:23 Julian Braha
2026-10-01 21:00 ` Frank Li
2026-10-05 13:40   ` Vinod Koul [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=asOo1HzrYIysrWF_@parshuram \
    --to=vkoul@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.li@oss.nxp.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=chleroy@kernel.org \
    --cc=colin.i.king@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=joao@joaoff.com \
    --cc=julianbraha@gmail.com \
    --cc=kees@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=rosenp@gmail.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

all inboxes | Powered by JetHome®