From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: sibyte: Remove unused config option SIBYTE_BCM1x55
Date: Fri, 17 Mar 2023 11:23:09 +0100 [thread overview]
Message-ID: <20230317102309.GC7054@alpha.franken.de> (raw)
In-Reply-To: <20230315135509.102542-1-tsbogend@alpha.franken.de>
On Wed, Mar 15, 2023 at 02:55:09PM +0100, Thomas Bogendoerfer wrote:
> SIBYTE_BCM1x55 is not selected anywhere, so let's get rid of it.
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
> arch/mips/Kbuild.platforms | 1 -
> arch/mips/sibyte/Kconfig | 13 +------------
> arch/mips/sibyte/Makefile | 2 --
> arch/mips/sibyte/Platform | 4 ----
> arch/mips/sibyte/common/bus_watcher.c | 4 ++--
> arch/mips/sibyte/common/cfe.c | 2 +-
> arch/mips/sibyte/common/sb_tbprof.c | 10 +++++-----
> arch/mips/sibyte/swarm/setup.c | 6 +++---
> 8 files changed, 12 insertions(+), 30 deletions(-)
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:[~2023-03-17 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 13:55 [PATCH] MIPS: sibyte: Remove unused config option SIBYTE_BCM1x55 Thomas Bogendoerfer
2023-03-17 10:23 ` 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=20230317102309.GC7054@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--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