From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: "David S . Miller" <davem@davemloft.net>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-ide@vger.kernel.org, linux-mips@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
b.zolnierkie@samsung.com
Subject: [PATCH 0/3] ide/MIPS/docs: remove no longer used au1xxx-ide driver
Date: Thu, 16 Jan 2020 13:29:35 +0100 [thread overview]
Message-ID: <20200116122938.20789-1-b.zolnierkie@samsung.com> (raw)
In-Reply-To: CGME20200116122951eucas1p1d36493f2b496bb13dca4fd1a17abad49@eucas1p1.samsung.com
Hi,
Commit 54ff4a1d1732 ("MIPS: Alchemy: pata_platform for DB1200")
from year 2014 converted the only user of au1xxx-ide IDE host
driver (MIPS Alchemy DB1200 platform) to use pata_platform libata
host driver instead. This patch series removes dead au1xxx-ide
driver code & co.
Since patch #2 depends on patch #1 (and it is also the best to
apply patch #3 after driver code removal) it would be probably
easiest to merge everything through MIPS tree (after getting
necessary ACKs, from David for the first patch and Jonathan for
the third one).
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
Bartlomiej Zolnierkiewicz (3):
ide: remove no longer used au1xxx-ide driver
MIPS: Alchemy: remove no longer used au1xxx_ide.h header
docs: mips: remove no longer needed au1xxx_ide.rst documentation
Documentation/mips/au1xxx_ide.rst | 130 ----
Documentation/mips/index.rst | 2 -
.../mips/include/asm/mach-au1x00/au1xxx_ide.h | 178 ------
drivers/ide/Kconfig | 17 -
drivers/ide/Makefile | 2 -
drivers/ide/au1xxx-ide.c | 597 ------------------
6 files changed, 926 deletions(-)
delete mode 100644 Documentation/mips/au1xxx_ide.rst
delete mode 100644 arch/mips/include/asm/mach-au1x00/au1xxx_ide.h
delete mode 100644 drivers/ide/au1xxx-ide.c
--
2.24.1
next parent reply other threads:[~2020-01-16 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200116122951eucas1p1d36493f2b496bb13dca4fd1a17abad49@eucas1p1.samsung.com>
2020-01-16 12:29 ` Bartlomiej Zolnierkiewicz [this message]
[not found] ` <CGME20200116122951eucas1p27bed87e1d46b5e1d8fc91abc33cd013a@eucas1p2.samsung.com>
2020-01-16 12:29 ` [PATCH 1/3] ide: remove no longer used au1xxx-ide driver Bartlomiej Zolnierkiewicz
2020-01-30 10:02 ` David Miller
[not found] ` <CGME20200116122952eucas1p13d84992633afb27c59358c120bc7781e@eucas1p1.samsung.com>
2020-01-16 12:29 ` [PATCH 2/3] MIPS: Alchemy: remove no longer used au1xxx_ide.h header Bartlomiej Zolnierkiewicz
[not found] ` <CGME20200116122952eucas1p2060adca6613ae02096ecc80319e5d197@eucas1p2.samsung.com>
2020-01-16 12:29 ` [PATCH 3/3] docs: mips: remove no longer needed au1xxx_ide.rst documentation Bartlomiej Zolnierkiewicz
2020-03-02 14:53 ` Bartlomiej Zolnierkiewicz
2020-01-16 12:52 ` [PATCH 0/3] ide/MIPS/docs: remove no longer used au1xxx-ide driver Manuel Lauss
2020-01-17 8:11 ` Christoph Hellwig
2020-01-24 23:03 ` Paul Burton
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=20200116122938.20789-1-b.zolnierkie@samsung.com \
--to=b.zolnierkie@samsung.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=jhogan@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.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 NNTP newsgroup(s).