linux-kernel - Re: [PATCH] nvme/quirk: Add a delay before checking device ready for memblaze device

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: <71e083c9-6bef-2da1-5eeb-fa6c6028c8c3@fb.com>
Date:   Thu, 8 Sep 2016 09:02:30 -0600
From:   Jens Axboe <axboe@...com>
To:     Keith Busch <keith.busch@...el.com>,
        Wang Weber <mail.weber.wang@...il.com>
CC:     <linux-nvme@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] nvme/quirk: Add a delay before checking device ready for
 memblaze device

On 09/08/2016 08:30 AM, Jens Axboe wrote:
> On 09/08/2016 08:36 AM, Keith Busch wrote:
>> On Thu, Sep 08, 2016 at 11:36:34AM +0800, Wang Weber wrote:
>>> Hi Jens,
>>>
>>> The following email was sent before, but it seems to be blocked since I
>>> received some messages about sending failure. So resend it with Google
>>> email account.
>>
>> You're still sending non plain text email, so it's going to be rejected
>> by the mailing list filter. It also mangles your patch such that it
>> won't cleanly apply. You have to use plain text for this to work well.
>
> Indeed. And in addition to it being rejected by the reflector, it also
> means your patch is mangled.

I guess Keith already made that point too on the patch mangling, needs
more coffee. Also, it mangles the patch.

-- 
Jens Axboe