Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c

From: Martin K. Petersen
Date: Wed Jan 29 2020 - 12:47:19 EST

Next message: Marek Szyprowski: "Re: [PATCH v2] dmaengine: Create symlinks between DMA channels and slaves"
Previous message: Nicolas Pitre: "Re: [PATCH] kbuild: allow symbol whitelisting with TRIM_UNUSED_KSYMS"
In reply to: Christoph Hellwig: "Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c"
Next in thread: Bartlomiej Zolnierkiewicz: "[PATCH 27/28] ata: move ata_eh_analyze_ncq_error() & co. to libata-core-sata.c"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Christoph,

> On Tue, Jan 28, 2020 at 02:33:39PM +0100, Bartlomiej Zolnierkiewicz wrote:
>> * include libata-scsi-sata.c in the build when CONFIG_SATA_HOST=y
>
> The libata-core.c vs libata-scsi.c split already is a bit weird, any
> reason not to simply have a single libata-sata.c?

I agree, I also tripped over libata-scsi-sata.

--
Martin K. Petersen Oracle Linux Engineering

Next message: Marek Szyprowski: "Re: [PATCH v2] dmaengine: Create symlinks between DMA channels and slaves"
Previous message: Nicolas Pitre: "Re: [PATCH] kbuild: allow symbol whitelisting with TRIM_UNUSED_KSYMS"
In reply to: Christoph Hellwig: "Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c"
Next in thread: Bartlomiej Zolnierkiewicz: "[PATCH 27/28] ata: move ata_eh_analyze_ncq_error() & co. to libata-core-sata.c"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]