From: Damien Le Moal <dlemoal@kernel.org>
To: Paolo Pisati <p.pisati@gmail.com>,
Niklas Cassel <cassel@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-ide@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH v2 1/2] m68k: amiga_defconfig: enable PATA_CSWARP
Date: Mon, 24 Mar 2025 06:53:17 -0400 [thread overview]
Message-ID: <c874f648-8583-4c6c-9ce5-5ba369ccc731@kernel.org> (raw)
In-Reply-To: <20250324092409.99430-2-p.pisati@gmail.com>
On 2025/03/24 5:24, Paolo Pisati wrote:
> Signed-off-by: Paolo Pisati <p.pisati@gmail.com>
> ---
> arch/m68k/configs/amiga_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/m68k/configs/amiga_defconfig b/arch/m68k/configs/amiga_defconfig
> index c705247e7b5b..feed92c95394 100644
> --- a/arch/m68k/configs/amiga_defconfig
> +++ b/arch/m68k/configs/amiga_defconfig
> @@ -334,6 +334,7 @@ CONFIG_ATA=y
> # CONFIG_ATA_VERBOSE_ERROR is not set
> # CONFIG_ATA_BMDMA is not set
> CONFIG_PATA_GAYLE=y
> +CONFIG_PATA_CSWARP=y
This needs to be patch 2, otherwise there will be some bisectability issues.
Unless Geert wants to take this patch and we queue patch 1 (the driver) through
libata tree.
Geert,
How do yu want to proceed ? We can take everything through libata, or you can
take both patches through your tree. I do not have a strong preference either way.
> CONFIG_PATA_BUDDHA=y
> CONFIG_MD=y
> CONFIG_BLK_DEV_DM=m
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-03-24 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 9:24 [PATCH v2 0/2] m68k: pata_cswarp: Add Amiga cslab ata support Paolo Pisati
2025-03-24 9:24 ` [PATCH v2 1/2] m68k: amiga_defconfig: enable PATA_CSWARP Paolo Pisati
2025-03-24 10:53 ` Damien Le Moal [this message]
2025-03-24 12:58 ` Geert Uytterhoeven
2025-03-24 9:24 ` [PATCH v2 2/2] ata: pata_cswarp: Add Amiga cslab ata support Paolo Pisati
2025-03-24 11:00 ` Damien Le Moal
2025-03-24 12:02 ` Paolo Pisati
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=c874f648-8583-4c6c-9ce5-5ba369ccc731@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=p.pisati@gmail.com \
/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