linux-kernel - Re: [PATCH 0/2] nvme: Improvements in sysfs entry for NVMe CMBs

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: <365e0b2b-06b1-dc0b-a9ae-dc901ca98d6a@fb.com>
Date:   Fri, 16 Dec 2016 12:23:28 -0700
From:   Jens Axboe <axboe@...com>
To:     Stephen Bates <sbates@...thlin.com>,
        <linux-kernel@...r.kernel.org>, <linux-nvme@...ts.infradead.org>,
        <linux-block@...r.kernel.org>
CC:     <sagi@...mberg.me>, <james_p_freyensee@...ux.intel.com>,
        <jonathan.derrick@...el.com>
Subject: Re: [PATCH 0/2] nvme: Improvements in sysfs entry for NVMe CMBs

On 12/16/2016 11:54 AM, Stephen Bates wrote:
> Hi
> 
> This series adds some more verbosity to the NVMe CMB sysfs entry.
> 
> Jens I based this off v4.9 because for some reason your for-4.10/block
> is missing my original CMB commit (202021c1a63c6)?

for-4.10/block was forked off v4.9-rc1, and that patch didn't make it
in until v4.9-rc2. Since for-4.10/block has been merged, any patches
for this series or next should be based on my for-linus, or just master.

Assuming these two apply directly to master as well?

-- 
Jens Axboe