From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH] MIPS: remove unused <asm/amon.h> header
Date: Sat, 26 Sep 2026 11:38:04 +0200 [thread overview]
Message-ID: <areSfI6haTEVitBy@alpha.franken.de> (raw)
In-Reply-To: <20260918025757.389718-1-enelsonmoore@gmail.com>
On Thu, Sep 17, 2026 at 07:57:51PM -0700, Ethan Nelson-Moore wrote:
> The last use of arch/mips/include/asm/amon.h was removed in
> commit 7fb6f7b0af67 ("MIPS: Remove deprecated CONFIG_MIPS_CMP"),
> but it was left behind. Remove it.
>
> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
> ---
> arch/mips/include/asm/amon.h | 12 ------------
> 1 file changed, 12 deletions(-)
> delete mode 100644 arch/mips/include/asm/amon.h
>
> diff --git a/arch/mips/include/asm/amon.h b/arch/mips/include/asm/amon.h
> deleted file mode 100644
> index 3cc03c64a9c7..000000000000
> --- a/arch/mips/include/asm/amon.h
> +++ /dev/null
> @@ -1,12 +0,0 @@
> -/*
> - * This file is subject to the terms and conditions of the GNU General Public
> - * License. See the file "COPYING" in the main directory of this archive
> - * for more details.
> - *
> - * Copyright (C) 2013 Imagination Technologies Ltd.
> - *
> - * Arbitrary Monitor Support (AMON)
> - */
> -int amon_cpu_avail(int cpu);
> -int amon_cpu_start(int cpu, unsigned long pc, unsigned long sp,
> - unsigned long gp, unsigned long a0);
> --
> 2.43.0
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:[~2026-09-26 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 2:57 [PATCH] MIPS: remove unused <asm/amon.h> header Ethan Nelson-Moore
2026-09-26 9:38 ` 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=areSfI6haTEVitBy@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=enelsonmoore@gmail.com \
--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