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

From: Christoph Hellwig
Date: Wed Jan 29 2020 - 12:32:01 EST

Next message: Tetsuo Handa: "Re: KASAN: slab-out-of-bounds Write in vgacon_scroll"
Previous message: Christoph Hellwig: "Re: [PATCH 15/28] ata: move sata_print_link_status() to libata-core-sata.c"
In reply to: Bartlomiej Zolnierkiewicz: "Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c"
Next in thread: Martin K. Petersen: "Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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?

Next message: Tetsuo Handa: "Re: KASAN: slab-out-of-bounds Write in vgacon_scroll"
Previous message: Christoph Hellwig: "Re: [PATCH 15/28] ata: move sata_print_link_status() to libata-core-sata.c"
In reply to: Bartlomiej Zolnierkiewicz: "Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c"
Next in thread: Martin K. Petersen: "Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]