From: Michael Ellerman <mpe@ellerman.id.au>
To: Ian Munsie <imunsie@au1.ibm.com>
Cc: Matt Ochs <mrochs@us.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>, mikey <mikey@neuling.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] cxl: add set/get private data to context struct
Date: Wed, 19 Aug 2015 15:33:16 +1000 [thread overview]
Message-ID: <1439962396.24918.8.camel@ellerman.id.au> (raw)
In-Reply-To: <1439960447-sup-3936@delenn.ozlabs.ibm.com>
On Wed, 2015-08-19 at 15:12 +1000, Ian Munsie wrote:
> Excerpts from Michael Ellerman's message of 2015-08-19 14:49:30 +1000:
> > Do we really need the accessors? They don't buy anything I can see over just
> > using ctx->priv directly.
>
> The reasoning there is because we don't currently expose the contents of
> stuct cxl_context to afu drivers, rather they just treat it as an opaque
> type.
>
> We could potentially change this to expose the details, but there's a
> lot of junk in there that's just internal details of the cxl driver that
> isn't of interest to an afu driver that I'd rather not expose.
>
> We also already have another accessor function (cxl_process_element) in
> the api, so it's not out of place.
>
> FWIW I'm not opposed to changing how this api works if it ultimately
> makes things better, but I want to wait until the cxlflash superpipe
> support is merged so any patches that change the api can change it at
> the same time.
OK. I saw struct cxl_context in cxl.h and figured it was public, but it's in
drivers/misc/cxl/cxl.h, so yes other drivers have no business poking in there,
even though they *could*.
So that's fine.
cheers
next prev parent reply other threads:[~2015-08-19 5:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 4:19 [PATCH 1/2] cxl: Add mechanism for delivering AFU driver specific events Ian Munsie
2015-08-19 4:19 ` [PATCH 2/2] cxl: add set/get private data to context struct Ian Munsie
2015-08-19 4:49 ` Michael Ellerman
2015-08-19 5:12 ` Ian Munsie
2015-08-19 5:33 ` Michael Ellerman [this message]
2015-08-19 5:30 ` [PATCH 1/2] cxl: Add mechanism for delivering AFU driver specific events Michael Ellerman
2015-08-19 7:03 ` Ian Munsie
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=1439962396.24918.8.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mrochs@us.ibm.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: 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
all inboxes | Powered by JetHome®