From: "Neil Armstrong" <neil.armstrong@linaro.org>
To: soc@kernel.org, arm@kernel.org
Cc: linux-oxnas@groups.io, linux-arm-kernel@lists.infradead.org
Subject: [PULL] final oxnas removal for 6.6
Date: Mon, 14 Aug 2023 10:32:33 +0200 [thread overview]
Message-ID: <3f91bb89-bf7b-d967-a302-2a8e1b0c3b01@linaro.org> (raw)
Hi,
Please pull this PR to remove all the remaining files for OXNAS support.
The other patches have been merged by the respective maintainers, Mark acked
for routing the irq-versatile changes via a SoC PR.
Thanks,
Neil
The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/narmstrong/linux-oxnas.git tags/oxnas-final-for-6.6
for you to fetch changes up to b1627ad5f457c8cea08bb2ab6b24d1c0381fbe30:
MAINTAINERS: remove OXNAS entry (2023-08-14 10:26:56 +0200)
----------------------------------------------------------------
Final OXNAS removal PR for v6.6:
- Remove irq-versatile-fpga compatible entry
- Mark irq-versatile-fpga oxnas compatible as deprecated
- Remove OXNAS maintainers entry
----------------------------------------------------------------
Neil Armstrong (3):
irqchip: irq-versatile-fpga: remove obsolete oxnas compatible
dt-bindings: interrupt-controller: arm,versatile-fpga-irq: mark oxnas compatible as deprecated
MAINTAINERS: remove OXNAS entry
.../bindings/interrupt-controller/arm,versatile-fpga-irq.txt | 4 +++-
MAINTAINERS | 10 ----------
drivers/irqchip/irq-versatile-fpga.c | 1 -
3 files changed, 3 insertions(+), 12 deletions(-)
reply other threads:[~2023-08-14 8:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3f91bb89-bf7b-d967-a302-2a8e1b0c3b01@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-oxnas@groups.io \
--cc=soc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).