linux-kernel - Re: [PATCH 3/3] block: remove last remaining traces of IDE documentation

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: <056303ce-1837-4d1e-a9fb-3e20e3686d59@infradead.org>
Date:   Fri, 6 May 2022 13:27:11 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Paul Gortmaker <paul.gortmaker@...driver.com>,
        Phillip Potter <phil@...lpotter.co.uk>
Cc:     Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
        Jens Axboe <axboe@...nel.dk>, Christoph Hellwig <hch@....de>
Subject: Re: [PATCH 3/3] block: remove last remaining traces of IDE
 documentation



On 5/6/22 13:24, Paul Gortmaker wrote:
> [Re: [PATCH 3/3] block: remove last remaining traces of IDE documentation] On 06/05/2022 (Fri 18:54) Phillip Potter wrote:
> 
>> On Fri, May 06, 2022 at 11:32:41AM -0400, Paul Gortmaker wrote:
> 
> [...]
> 
>>> Are you working off linux-next?  If not, what is your baseline and what
>>> are you running and what do you see?  For example, the commands below:
>>>
>>> The ecb86 that I sent in this e-mail still applies on linux-next of
>>> today which contains Jens next as you can see:
>>>
>>
>> I was yes, the point I was trying to make (poorly) is that your patch
>> conflicts with Randy's patch which itself is not yet in linux-next, as
>> normally I send everything together at the start of the merge window to
>> Jens, as I don't have my own kernel.org tree yet, and usually I only get
>> one or two patches in a cycle anyway.
>>
>> This is not your fault, you couldn't have been expected to know this in
>> retrospect, and I should probably look into getting my own tree/GPG key
>> sorted to alleviate this problem in future.
>>
>> In the meantime, if you're comfortable with the idea, I can just resolve
>> the conflict myself when I send the patches onto Jens this time and
>> include patch 3/3 pre-fixed up. Merge window will be fairly soon anyway.
> 
> Sure, go ahead - just fix up things so all the last bits are gone; don't
> even worry about patch attribution; I don't care about that.

Thank for the cleanups, Paul.

-- 
~Randy