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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200129173156.GL12616@infradead.org>
Date:   Wed, 29 Jan 2020 09:31:56 -0800
From:   Christoph Hellwig <hch@...radead.org>
To:     Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
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 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?