From: Max Staudt <max@enpas.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: 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] m68k: defconfig: Update defconfigs for v5.4-rc1
Date: Mon, 4 Nov 2019 22:15:53 +0100 [thread overview]
Message-ID: <65699814-9260-643e-10e0-e1be9929b957@enpas.org> (raw)
In-Reply-To: <CAMuHMdX3+-JO68LGE-NuT9axRUj3=bbtpDZ8E3v5UNoj5ctLHg@mail.gmail.com>
On 11/04/2019 12:06 PM, Geert Uytterhoeven wrote:
>> As for the Amiga defconfig, how about moving from IDE drivers to ATA?
>>
>> The old IDE stack is slated for removal in less than 2 years, and people should probably move over to libata instead.
>>
>> How about the following changes?
>> Is there any Amiga IDE controller left without a libata equivalent?
>>
>> CONFIG_IDE=n
>> CONFIG_IDE_GD_ATAPI=n
>> CONFIG_BLK_DEV_IDECD=n
>> CONFIG_BLK_DEV_GAYLE=n
>> CONFIG_BLK_DEV_BUDDHA=n
>>
>> CONFIG_ATA=y
>> CONFIG_ATA_VERBOSE_ERROR=y
>> CONFIG_PATA_GAYLE=y
>> CONFIG_PATA_BUDDHA=y
>
> Amiga is fine.
>
> Mac and Q40 are not, apparently.
Sigh. I guess we have to keep CONFIG_IDE then. Thank you for checking!
How about:
CONFIG_BLK_DEV_GAYLE=n
CONFIG_BLK_DEV_BUDDHA=n
CONFIG_ATA=y
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_PATA_GAYLE=y
CONFIG_PATA_BUDDHA=y
for the multi_defconfig, and the following *only* for amiga_defconfig (as it's useless without drivers on Amiga):
CONFIG_IDE=n
CONFIG_IDE_GD_ATAPI=n
CONFIG_BLK_DEV_IDECD=n
Max
next prev parent reply other threads:[~2019-11-04 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 7:35 [PATCH] m68k: defconfig: Update defconfigs for v5.4-rc1 Geert Uytterhoeven
2019-10-01 10:55 ` Max Staudt
2019-10-07 14:11 ` Max Staudt
2019-11-04 11:06 ` Geert Uytterhoeven
2019-11-04 21:15 ` Max Staudt [this message]
2019-11-05 0:01 ` Christoph Hellwig
2019-11-05 0:14 ` John Paul Adrian Glaubitz
2019-11-05 0:53 ` Brad Boyer
2019-11-05 2:33 ` Finn Thain
2019-11-05 3:19 ` Brad Boyer
2019-11-05 4:13 ` Finn Thain
2019-11-05 20:36 ` Brad Boyer
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=65699814-9260-643e-10e0-e1be9929b957@enpas.org \
--to=max@enpas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.