> -----Original Message----- > From: linux-block-ow...@vger.kernel.org [mailto:linux-block- > ow...@vger.kernel.org] On Behalf Of Jon Derrick > Sent: Thursday, February 16, 2017 10:15 AM > To: Michael Ellerman <m...@ellerman.id.au> > Cc: Jens Axboe <ax...@kernel.dk>; Rafael Antognolli > <rafael.antogno...@intel.com>; Greg Kroah-Hartman > <gre...@linuxfoundation.org>; linux-ker...@vger.kernel.org; linux- > bl...@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; Christoph Hellwig > <h...@lst.de>; Scott Bauer <scott.ba...@intel.com> > Subject: Re: [PATCHv3 4/4] MAINTAINERS: Remove powerpc's opal match > > Thanks everyone. Sorry about the mess :) > > On 02/15/2017 10:23 PM, Michael Ellerman wrote: > > Jon Derrick <jonathan.derr...@intel.com> writes: > > > >> PPC's 'opal' match pattern also matches block/sed-opal.c, where it looks > >> 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", > > that should be pretty unique? > > > > ... :)
The library could easily be used for devices supporting the Opalite and Pyrite SSCs, not just the Opal SSC. With some effort, I suspect that Enterprise SSC 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
