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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Bartlomiej Zolnierkiewicz <b.zolnierkie@xxxxxxxxxxx>
Subject: Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 29 Jan 2020 09:31:56 -0800
Cc: Jens Axboe <axboe@xxxxxxxxx>, Michael Schmitz <schmitzmic@xxxxxxxxx>, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>, linux-ide@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20200128133343.29905-25-b.zolnierkie@samsung.com>
References: <20200128133343.29905-1-b.zolnierkie@samsung.com> <CGME20200128133418eucas1p157933935f14f9c83c604bc5dc38bcbae@eucas1p1.samsung.com> <20200128133343.29905-25-b.zolnierkie@samsung.com>

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?

Follow-Ups:
- Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c
  - From: Martin K. Petersen

References:
- [PATCH 00/28] ata: optimize core code size on PATA only setups
  - From: Bartlomiej Zolnierkiewicz
- [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c
  - From: Bartlomiej Zolnierkiewicz

Prev by Date: Re: [PATCH 15/28] ata: move sata_print_link_status() to libata-core-sata.c
Next by Date: Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c
Previous by thread: Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c
Next by thread: Re: [PATCH 24/28] ata: start separating SATA specific code from libata-scsi.c
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystems] [Linux SCSI] [Linux RAID] [Git] [Kernel Newbies] [Linux Newbie] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Samba] [Device Mapper]