Message ID | cover.1623131194.git.fthain@linux-m68k.org |
---|---|
Headers | show |
Series | Use libata platform drivers to replace deprecated m68k IDE drivers | expand |
On Tue, Jun 08, 2021 at 03:46:34PM +1000, Finn Thain wrote: > This patch series allows m68k platforms to switch from deprecated IDE > drivers to libata drivers. Thanks, this looks good to me: Reviewed-by: Christoph Hellwig <hch@lst.de> Jens, any chance you could pick this up quickly to prepare for the legacy IDE removal series?
On 6/8/21 8:37 AM, Christoph Hellwig wrote: > On Tue, Jun 08, 2021 at 03:46:34PM +1000, Finn Thain wrote: >> This patch series allows m68k platforms to switch from deprecated IDE >> drivers to libata drivers. > > Thanks, this looks good to me: > > Reviewed-by: Christoph Hellwig <hch@lst.de> > > Jens, any chance you could pick this up quickly to prepare for the > legacy IDE removal series? I can, but had assumed it'd go through the IDE tree. But not that important I guess. I've queued it up for now.
Hi Jens, please note that Finn's patch depends on one of mine currently under review. Without that one, Q40 support may break in certain cases. Cheers, Michael Schmitz On 9/06/21 9:04 am, Jens Axboe wrote: > On 6/8/21 8:37 AM, Christoph Hellwig wrote: >> On Tue, Jun 08, 2021 at 03:46:34PM +1000, Finn Thain wrote: >>> This patch series allows m68k platforms to switch from deprecated IDE >>> drivers to libata drivers. >> Thanks, this looks good to me: >> >> Reviewed-by: Christoph Hellwig <hch@lst.de> >> >> Jens, any chance you could pick this up quickly to prepare for the >> legacy IDE removal series? > I can, but had assumed it'd go through the IDE tree. But not that > important I guess. I've queued it up for now. >
On Wed, 9 Jun 2021, Michael Schmitz wrote: > please note that Finn's patch depends on one of mine currently under review. > Without that one, Q40 support may break in certain cases. > AFAIK, that's only true for a configuration that enables both CONFIG_Q40 and CONFIG_ATARI. In my tests with stock v5.12, such a configuration presently doesn't work correctly on Atari. This patch series doesn't make this issue any worse. Besides, I think it is a non-issue because the problem is so rare that no-one noticed it before I did, and the workaround for CONFIG_Q40 users is trivial anyway (disable CONFIG_ATARI). Is there really some benefit in holding up this patch series?
Hi Finn, Am 09.06.2021 um 15:53 schrieb Finn Thain: > On Wed, 9 Jun 2021, Michael Schmitz wrote: > >> please note that Finn's patch depends on one of mine currently under review. >> Without that one, Q40 support may break in certain cases. >> > > AFAIK, that's only true for a configuration that enables both CONFIG_Q40 > and CONFIG_ATARI. In my tests with stock v5.12, such a configuration > presently doesn't work correctly on Atari. > > This patch series doesn't make this issue any worse. You're right, it's not a regression (that combination was broken before) , and there's no patch dependency or conflict either. > Besides, I think it is a non-issue because the problem is so rare that > no-one noticed it before I did, and the workaround for CONFIG_Q40 users is > trivial anyway (disable CONFIG_ATARI). > > Is there really some benefit in holding up this patch series? On second thought - no point in holding this up. Cheers, Michael
On 6/8/21 3:50 PM, Michael Schmitz wrote: > Hi Jens, > > please note that Finn's patch depends on one of mine currently under > review. Without that one, Q40 support may break in certain cases. Can you point me at it?
Hi Jens, it's this one: https://lore.kernel.org/linux-m68k/1623223322-4242-1-git-send-email-schmitzmic@gmail.com/ But see my reply to Finn's mail - my patch is entirely orthogonal to his, and simply fixes a long standing issue that has recently surfaced with Finn's efforts to unify Atari and Q40 IDE drivers. Cheers, Michael On 10/06/21 3:23 am, Jens Axboe wrote: > On 6/8/21 3:50 PM, Michael Schmitz wrote: >> Hi Jens, >> >> please note that Finn's patch depends on one of mine currently under >> review. Without that one, Q40 support may break in certain cases. > Can you point me at it? >