From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Joshua Thompson <funaho@jurai.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] ide/macide: Convert Mac IDE driver to platform driver
Date: Sat, 12 Sep 2020 09:07:22 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.23.453.2009120812020.8@nippy.intranet> (raw)
In-Reply-To: <CAMuHMdU9vEUasHMeS=OiHX+16dgQGPdmjEtCi+-YLcXvw4BM7g@mail.gmail.com>
On Fri, 11 Sep 2020, Geert Uytterhoeven wrote:
>
> Sorry, I completely missed that the Baboon case registers a
> "pata_platform" device instead of a "macide" device. Hence please
> ignore my comments related to that. Sorry for the noise.
>
No problem. That misunderstanding got me thinking about implications
stemming from my patch that I may have overlooked. Here's what I found.
1) Your presumption that the old macide driver would keep supporting all
variants does make sense, as that would delay disruption for as long as
possible (i.e. for as long as the IDE subsystem remains).
However, if my patch does not get merged until 2021, that disruption would
not arrive earlier than promised by commit 7ad19a99ad431 ("ide: officially
deprecated the legacy IDE driver").
2) My patch omitted a mac_defconfig update that would enable an
alternative driver for the Baboon case. I will remedy this in v2.
3) It turns out that the Debian/m68k kernel config has
CONFIG_BLK_DEV_PLATFORM=m. This will work fine with this patch. (I assume
that Debian developers will replace CONFIG_BLK_DEV_PLATFORM with
CONFIG_PATA_PLATFORM prior to the removal of the IDE subsystem next year.)
prev parent reply other threads:[~2020-09-11 23:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 7:42 [PATCH] ide/macide: Convert Mac IDE driver to platform driver Finn Thain
2020-09-09 8:21 ` Geert Uytterhoeven
2020-09-10 0:23 ` Finn Thain
2020-09-10 3:44 ` Michael Schmitz
2020-09-10 6:26 ` Geert Uytterhoeven
2020-09-10 23:05 ` Finn Thain
2020-09-11 6:28 ` Geert Uytterhoeven
2020-09-11 23:07 ` Finn Thain [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=alpine.LNX.2.23.453.2009120812020.8@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=b.zolnierkie@samsung.com \
--cc=davem@davemloft.net \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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