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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <63839ddc-a19e-62b1-30b6-8394eee1887a@samsung.com>
Date:   Fri, 7 Feb 2020 15:25:09 +0100
From:   Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
To:     "Martin K. Petersen" <martin.petersen@...cle.com>,
        Christoph Hellwig <hch@...radead.org>
Cc:     Jens Axboe <axboe@...nel.dk>,
        Michael Schmitz <schmitzmic@...il.com>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 24/28] ata: start separating SATA specific code from
 libata-scsi.c


On 1/29/20 6:46 PM, Martin K. Petersen wrote:
> 
> 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.

Fixed in v2 version of the patchset.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics