From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-sgx@vger.kernel.org, akpm@linux-foundation.org,
dave.hansen@intel.com, sean.j.christopherson@intel.com,
nhorman@redhat.com, npmccallum@redhat.com, serge.ayoun@intel.com,
shay.katz-zamir@intel.com, haitao.huang@intel.com,
andriy.shevchenko@linux.intel.com, tglx@linutronix.de,
kai.svahn@intel.com, bp@alien8.de, josh@joshtriplett.org,
luto@kernel.org, kai.huang@intel.com, rientjes@google.com,
cedric.xing@intel.com, puiterwijk@redhat.com,
linux-security-module@vger.kernel.org,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [PATCH v23 12/24] x86/sgx: Linux Enclave Driver
Date: Mon, 9 Dec 2019 21:57:19 +0200 [thread overview]
Message-ID: <20191209195719.GH19243@linux.intel.com> (raw)
In-Reply-To: <20191207080939.GA193518@kroah.com>
On Sat, Dec 07, 2019 at 09:09:39AM +0100, Greg KH wrote:
> On Fri, Dec 06, 2019 at 10:38:07PM +0200, Jarkko Sakkinen wrote:
> > > Why a whole cdev?
> > >
> > > Why not use a misc device? YOu only have 2 devices right? Why not 2
> > > misc devices then? That saves the use of a whole major number and makes
> > > your code a _LOT_ simpler.
> >
> > The downside would be that if we ever want to add sysfs attributes, that
> > could not be done synchronously with the device creation.
>
> That is what the groups member of struct misc_device is for.
OK, cool, then there is no problem changing to misc.
I haven't seen misc drivers (not that I've looked through every single
of them so I suppose there are such) to use it and somehow have been
blind to seeing it that it si there.
Thanks again for the feedback. I'll fix this for the next patch set
version.
/Jarkko
next prev parent reply other threads:[~2019-12-09 19:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191028210324.12475-1-jarkko.sakkinen@linux.intel.com>
2019-10-28 21:03 ` [PATCH v23 12/24] x86/sgx: Linux Enclave Driver Jarkko Sakkinen
2019-10-29 9:29 ` Jarkko Sakkinen
2019-10-30 9:30 ` Sean Christopherson
2019-10-31 21:12 ` Jarkko Sakkinen
2019-11-05 11:11 ` Jarkko Sakkinen
2019-11-08 8:20 ` Jarkko Sakkinen
2019-10-30 13:45 ` Stephen Smalley
2019-10-31 21:17 ` Jarkko Sakkinen
2019-11-01 13:16 ` Stephen Smalley
2019-11-01 13:28 ` Stephen Smalley
2019-11-01 15:32 ` Sean Christopherson
2019-11-01 17:16 ` Stephen Smalley
2019-11-08 8:05 ` Jarkko Sakkinen
2019-11-28 18:24 ` Greg KH
2019-12-06 20:38 ` Jarkko Sakkinen
2019-12-07 8:09 ` Greg KH
2019-12-09 19:57 ` Jarkko Sakkinen [this message]
2019-12-23 11:01 ` Jarkko Sakkinen
2019-10-28 21:03 ` [PATCH v23 15/24] x86/sgx: Add provisioning Jarkko Sakkinen
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=20191209195719.GH19243@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=cedric.xing@intel.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=haitao.huang@intel.com \
--cc=josh@joshtriplett.org \
--cc=kai.huang@intel.com \
--cc=kai.svahn@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=luto@kernel.org \
--cc=nhorman@redhat.com \
--cc=npmccallum@redhat.com \
--cc=puiterwijk@redhat.com \
--cc=rientjes@google.com \
--cc=sean.j.christopherson@intel.com \
--cc=serge.ayoun@intel.com \
--cc=shay.katz-zamir@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).