RE: [PATCHv3 4/4] MAINTAINERS: Remove powerpc's opal match
From: Elliott, Robert (Persistent Memory) <hidden>
Date: 2017-02-17 16:41:01
Also in:
linuxppc-dev, lkml
-----Original Message----- From: linux-block-owner@vger.kernel.org [mailto:linux-block- owner@vger.kernel.org] On Behalf Of Jon Derrick Sent: Thursday, February 16, 2017 10:15 AM To: Michael Ellerman <mpe@ellerman.id.au> Cc: Jens Axboe <axboe@kernel.dk>; Rafael Antognolli [off-list ref]; Greg Kroah-Hartman [off-list ref]; linux-kernel@vger.kernel.org; linux- block@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; Christoph Hellwig [off-list ref]; Scott Bauer [off-list ref] Subject: Re: [PATCHv3 4/4] MAINTAINERS: Remove powerpc's opal match =20 Thanks everyone. Sorry about the mess :) =20 On 02/15/2017 10:23 PM, Michael Ellerman wrote:quoted
Jon Derrick [off-list ref] writes:quoted
PPC's 'opal' match pattern also matches block/sed-opal.c, where it loo=
ks
quoted
quoted
like the 'arch/powerpc' file pattern should be enough to match powerpc opal code by itself. Remove the opal regex pattern from powerpc.We thought of it first. Can't you just rename your driver, Opal Storage Specification, so "oss"=
,
quoted
that should be pretty unique? ... :)
The library could easily be used for devices supporting the Opalite and Pyr= ite=20 SSCs, not just the Opal SSC. With some effort, I suspect that Enterprise SS= C could also be supported. So, a broader name might indeed be useful. The full names of the specifications are: TCG Storage Security Subsystem Class: Opal TCG Storage Security Subsystem Class: Opalite TCG Storage Security Subsystem Class: Pyrite TCG Storage Security Subsystem Class: Enterprise --- Robert Elliott, HPE Persistent Memory