From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 93816C48BCF for ; Wed, 9 Jun 2021 03:53:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 733A861181 for ; Wed, 9 Jun 2021 03:53:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233234AbhFIDzG (ORCPT ); Tue, 8 Jun 2021 23:55:06 -0400 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:34192 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233144AbhFIDzG (ORCPT ); Tue, 8 Jun 2021 23:55:06 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id 56E4029DD2; Tue, 8 Jun 2021 23:53:10 -0400 (EDT) Date: Wed, 9 Jun 2021 13:53:27 +1000 (AEST) From: Finn Thain To: Michael Schmitz cc: Jens Axboe , Christoph Hellwig , Geert Uytterhoeven , "David S. Miller" , Joshua Thompson , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org, Richard Zidlicky Subject: Re: [PATCH v2 0/2] Use libata platform drivers to replace deprecated m68k IDE drivers In-Reply-To: <36f7519d-698f-1284-551a-0dbd82e2a0d8@gmail.com> Message-ID: <1016d48a-a276-f7b0-49a8-4571f4f75a61@linux-m68k.org> References: <36f7519d-698f-1284-551a-0dbd82e2a0d8@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-ide@vger.kernel.org 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?