linux-kernel - Re: [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW 22301111

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]

Date:   Fri, 16 Aug 2019 14:01:26 -0600
From:   Keith Busch <kbusch@...nel.org>
To:     "Mario.Limonciello@...l.com" <Mario.Limonciello@...l.com>
Cc:     "sagi@...mberg.me" <sagi@...mberg.me>,
        "axboe@...com" <axboe@...com>, "hch@....de" <hch@....de>,
        "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Ryan.Hong@...l.com" <Ryan.Hong@...l.com>,
        "Crag.Wang@...l.com" <Crag.Wang@...l.com>,
        "sjg@...gle.com" <sjg@...gle.com>,
        "Charles.Hyde@...lteam.com" <Charles.Hyde@...lteam.com>,
        "Jared.Dominguez@...l.com" <Jared.Dominguez@...l.com>
Subject: Re: [PATCH v2] nvme: Add quirk for LiteON CL1 devices running FW
 22301111

On Fri, Aug 16, 2019 at 12:43:02PM -0700, Mario.Limonciello@...l.com wrote:
> > We need to coordinate with Jens, don't think its a good idea if I'll
> > just randomly get stuff from linus' tree and send an rc pull request.
> 
> The dependent commit is in Linus' tree now.
> 4eaefe8c621c6195c91044396ed8060c179f7aae
> 
> Also it was reported to me after this was submitted that the comment
> whitespace should have been aligned during the switchover from v1 to v2.
> 
> V1 the whitespace was further left since it was applying to 3 drives, but now
> that they're combined in v2 the whitespace wasn't adjusted.
> 
> Let me know if you want me to resubmit v3 w/ whitespace modification or
> if you will want to adjust that locally when you pull it in.

Go ahead and resend the patch with your fixes included. This is going to
have to wait till next week anyway in order to have a clean pull request
through our normal path to mainline.