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/mips-boards/sead3-addr.h> header
Date: Sat, 26 Sep 2026 11:38:26 +0200 [thread overview]
Message-ID: <areSkrgM1FDjlK_w@alpha.franken.de> (raw)
In-Reply-To: <20260918030041.397914-1-enelsonmoore@gmail.com>
On Thu, Sep 17, 2026 at 08:00:35PM -0700, Ethan Nelson-Moore wrote:
> The last use of arch/mips/include/asm/mips-boards/sead3-addr.h was
> removed in commit 64601cb1343f ("leds: Remove SEAD-3 driver") but it
> was left behind. Remove it.
>
> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
> ---
> .../mips/include/asm/mips-boards/sead3-addr.h | 83 -------------------
> 1 file changed, 83 deletions(-)
> delete mode 100644 arch/mips/include/asm/mips-boards/sead3-addr.h
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:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 3:00 [PATCH] MIPS: remove unused <asm/mips-boards/sead3-addr.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=areSkrgM1FDjlK_w@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