linux-kernel - Re: [PATCH v2 0/18] pata_parport: protocol drivers fixes and cleanups

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: <8a0bd9fb-c667-8871-1955-3e4eb880f43d@omp.ru>
Date:   Wed, 15 Feb 2023 20:14:51 +0300
From:   Sergey Shtylyov <s.shtylyov@....ru>
To:     Damien Le Moal <damien.lemoal@...nsource.wdc.com>,
        Ondrej Zary <linux@...y.sk>
CC:     Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
        Tim Waugh <tim@...erelk.net>, <linux-block@...r.kernel.org>,
        <linux-parport@...ts.infradead.org>, <linux-ide@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/18] pata_parport: protocol drivers fixes and cleanups

On 2/15/23 2:50 AM, Damien Le Moal wrote:
[...]
>> This patch series fixes two bugs and cleans up pata_parport protocol drivers,
>> making the code simpler with no changes in behavior (except logged messages).
>>
>> Signed-off-by: Ondrej Zary <linux@...y.sk>
> 
> Sergey did send you some reviewed-by tags for some of the patches. But I
> do not see any in this v2. Did you forget to add the tags to the reviewed
> patches ? That is nice to do so that I do not have to keep track of
> reviews across series versions...

   Yes, it would also simplify my further reviews (I have low bandwidth currently
due to being somewhat overload at work)...

>> ---
>> Changes in v2:
>>  - added two bugfixes (first two patches)
>>  - addressed Sergey's comments (mostly split patches)

   Well, you're supposed to be more detailed about what you really
did to the series, preferably listing the changes in each patch (usually
after the --- tearline)...

[...]

MBR, Sergey