From: Christoph Hellwig <hch@infradead.org> To: Scott Bauer <scott.bauer@intel.com> Cc: hch@infradead.org, sagi@grimberg.me, axboe@fb.com, linux-nvme@lists.infradead.org, keith.busch@intel.com, Rafael.Antognolli@intel.com, linux-block@vger.kernel.org, jonathan.derrick@intel.com, j.naumann@fu-berlin.de Subject: Re: [PATCH v1 1/7] Include: Add definitions for sed Date: Thu, 17 Nov 2016 07:22:15 -0800 [thread overview] Message-ID: <20161117152215.GA20335@infradead.org> (raw) In-Reply-To: <1479338252-8777-2-git-send-email-scott.bauer@intel.com> > @@ -0,0 +1,58 @@ > +/* > + * Copyright =A9 2016 Intel Corporation > + * > + * Permission is hereby granted, free of charge, to any person obtaining= a > + * copy of this software and associated documentation files (the "Softwa= re"), > + * to deal in the Software without restriction, including without limita= tion > + * the rights to use, copy, modify, merge, publish, distribute, sublicen= se, > + * and/or sell copies of the Software, and to permit persons to whom the > + * Software is furnished to do so, subject to the following conditions: > + * > + * The above copyright notice and this permission notice (including the = next > + * paragraph) shall be included in all copies or substantial portions of= the > + * Software. > + * > + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRE= SS OR > + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILI= TY, > + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SH= ALL > + * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR = OTHER > + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISI= NG > + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER D= EALINGS Can we get a proper GPLv2/GPLv2 license for this from the Intel layers? While the license grant looks fine from a quick look I'd really prefer to have an official statement that this should be compatible with the kernel licensing. > +#define LINUX_OPAL_H > + > +#include <linux/sed.h> > +#include <linux/kernel.h> > + > +enum { > + TCG_SECP_00 =3D 0, > + TCG_SECP_01, > +}; These are the SPC4 security protocol defintions, aren't they? Can you please add a separate include/scsi/sec_protocol.h header that defines just these and documents where they come from? Similarly for all the other constants it would be nice to refer to the spec they are from in the header. > +struct sec_ops { > + int (*send)(void *data, __u16 SPSP, __u8 SECP, > + void *buffer, size_t len, > + sec_cb *cb, void *cb_data); > + int (*recv)(void *data, __u16 SPSP, __u8 SECP, > + void *buffer, size_t len, > + sec_cb *cb, void *cb_data); please use lower case names for all arguments and variables. _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig) Subject: [PATCH v1 1/7] Include: Add definitions for sed Date: Thu, 17 Nov 2016 07:22:15 -0800 [thread overview] Message-ID: <20161117152215.GA20335@infradead.org> (raw) In-Reply-To: <1479338252-8777-2-git-send-email-scott.bauer@intel.com> > @@ -0,0 +1,58 @@ > +/* > + * Copyright ? 2016 Intel Corporation > + * > + * Permission is hereby granted, free of charge, to any person obtaining a > + * copy of this software and associated documentation files (the "Software"), > + * to deal in the Software without restriction, including without limitation > + * the rights to use, copy, modify, merge, publish, distribute, sublicense, > + * and/or sell copies of the Software, and to permit persons to whom the > + * Software is furnished to do so, subject to the following conditions: > + * > + * The above copyright notice and this permission notice (including the next > + * paragraph) shall be included in all copies or substantial portions of the > + * Software. > + * > + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR > + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, > + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL > + * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER > + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING > + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS Can we get a proper GPLv2/GPLv2 license for this from the Intel layers? While the license grant looks fine from a quick look I'd really prefer to have an official statement that this should be compatible with the kernel licensing. > +#define LINUX_OPAL_H > + > +#include <linux/sed.h> > +#include <linux/kernel.h> > + > +enum { > + TCG_SECP_00 = 0, > + TCG_SECP_01, > +}; These are the SPC4 security protocol defintions, aren't they? Can you please add a separate include/scsi/sec_protocol.h header that defines just these and documents where they come from? Similarly for all the other constants it would be nice to refer to the spec they are from in the header. > +struct sec_ops { > + int (*send)(void *data, __u16 SPSP, __u8 SECP, > + void *buffer, size_t len, > + sec_cb *cb, void *cb_data); > + int (*recv)(void *data, __u16 SPSP, __u8 SECP, > + void *buffer, size_t len, > + sec_cb *cb, void *cb_data); please use lower case names for all arguments and variables.
next prev parent reply other threads:[~2016-11-17 15:22 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-11-16 23:17 [PATCH v1 0/7] SED OPAL Library Scott Bauer 2016-11-16 23:17 ` Scott Bauer 2016-11-16 23:17 ` [PATCH v1 1/7] Include: Add definitions for sed Scott Bauer 2016-11-16 23:17 ` Scott Bauer 2016-11-17 15:22 ` Christoph Hellwig [this message] 2016-11-17 15:22 ` Christoph Hellwig 2016-11-17 16:10 ` Scott Bauer 2016-11-17 16:10 ` Scott Bauer 2016-11-16 23:17 ` [PATCH v1 2/7] lib: Add Sed-opal library Scott Bauer 2016-11-16 23:17 ` Scott Bauer 2016-11-17 0:35 ` Keith Busch 2016-11-17 0:35 ` Keith Busch 2016-11-17 15:38 ` Christoph Hellwig 2016-11-17 15:38 ` Christoph Hellwig 2016-11-16 23:17 ` [PATCH v1 3/7] lib: Add Sed to Kconfig and Makefile Scott Bauer 2016-11-16 23:17 ` Scott Bauer 2016-11-16 23:17 ` [PATCH v1 4/7] include: Add sec_ops to block device operations Scott Bauer 2016-11-16 23:17 ` Scott Bauer 2016-11-16 23:17 ` [PATCH v1 5/7] nvme: Implement SED Security Operations Scott Bauer 2016-11-16 23:17 ` Scott Bauer 2016-11-17 0:09 ` Keith Busch 2016-11-17 0:09 ` Keith Busch 2016-11-16 23:17 ` [PATCH v1 6/7] nvme: Implement SED Unlock from suspend Scott Bauer 2016-11-16 23:17 ` Scott Bauer 2016-11-17 13:16 ` Christoph Hellwig 2016-11-17 13:16 ` Christoph Hellwig 2016-11-16 23:17 ` [PATCH v1 7/7] block: ioctl: Wire up Sed to block ioctls Scott Bauer 2016-11-16 23:17 ` Scott Bauer 2016-11-17 13:12 ` [PATCH v1 0/7] SED OPAL Library Christoph Hellwig 2016-11-17 13:12 ` Christoph Hellwig 2016-11-17 17:36 ` Scott Bauer 2016-11-17 17:36 ` Scott Bauer 2016-11-17 18:21 ` Rafael Antognolli 2016-11-17 18:21 ` Rafael Antognolli 2016-11-17 19:28 ` Christoph Hellwig 2016-11-17 19:28 ` Christoph Hellwig 2016-11-17 19:33 ` Scott Bauer 2016-11-17 19:33 ` Scott Bauer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20161117152215.GA20335@infradead.org \ --to=hch@infradead.org \ --cc=Rafael.Antognolli@intel.com \ --cc=axboe@fb.com \ --cc=j.naumann@fu-berlin.de \ --cc=jonathan.derrick@intel.com \ --cc=keith.busch@intel.com \ --cc=linux-block@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=sagi@grimberg.me \ --cc=scott.bauer@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.