All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: Ian Munsie <imunsie@au1.ibm.com>,
	Michael Ellerman <michaele@au1.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Matt Ochs <mrochs@us.ibm.com>, Manoj Kumar <kumarmn@us.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Michael Neuling <mikey@neuling.org>
Subject: Re: [PATCH v3 2/2] cxl: add set/get private data to context struct
Date: Tue, 8 Mar 2016 18:59:49 +1100	[thread overview]
Message-ID: <56DE8675.5080001@au1.ibm.com> (raw)
In-Reply-To: <1457401715-26435-2-git-send-email-imunsie@au.ibm.com>

On 08/03/16 12:48, Ian Munsie wrote:
> From: Michael Neuling <mikey@neuling.org>
>
> This provides AFU drivers a means to associate private data with a cxl
> context. This is particularly intended for make the new callbacks for
> driver specific events easier for AFU drivers to use, as they can easily
> get back to any private data structures they may use.
>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
> Signed-off-by: Ian Munsie <imunsie@au1.ibm.com>
> Reviewed-by: Matthew R. Ochs <mrochs@linux.vnet.ibm.com>

Looks good to me.

Reviewed-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>

-- 
Andrew Donnellan              Software Engineer, OzLabs
andrew.donnellan@au1.ibm.com  Australia Development Lab, Canberra
+61 2 6201 8874 (work)        IBM Australia Limited

  reply	other threads:[~2016-03-08  8:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  1:48 [PATCH v3 1/2] cxl: Add mechanism for delivering AFU driver specific events Ian Munsie
2016-03-08  1:48 ` [PATCH v3 2/2] cxl: add set/get private data to context struct Ian Munsie
2016-03-08  7:59   ` Andrew Donnellan [this message]
2016-03-08  4:06 ` [PATCH v3 1/2] cxl: Add mechanism for delivering AFU driver specific events Matt Ochs
2016-03-08  7:59 ` Andrew Donnellan
2016-03-09  9:27 ` Frederic Barrat
2016-03-10  0:46   ` Ian Munsie
2016-03-10  1:26   ` Ian Munsie
2016-03-09 14:37 ` Vaibhav Jain
2016-03-09 16:41   ` Matt Ochs
2016-03-09 16:41     ` Matt Ochs
2016-03-09 17:08   ` Frederic Barrat
2016-03-10 17:19     ` Vaibhav Jain
2016-03-10 17:19       ` Vaibhav Jain
2016-03-10  1:18   ` Ian Munsie
2016-03-10 17:39     ` Vaibhav Jain
2016-03-11  1:48     ` Andrew Donnellan
2016-03-10  3:24   ` Michael Neuling
2016-03-10  3:24     ` Michael Neuling
2016-03-10 17:23     ` Vaibhav Jain

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=56DE8675.5080001@au1.ibm.com \
    --to=andrew.donnellan@au1.ibm.com \
    --cc=imunsie@au1.ibm.com \
    --cc=kumarmn@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michaele@au1.ibm.com \
    --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 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.