From: Philippe Bergheaud <felix@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, mikey@neuling.org,
mrochs@linux.vnet.ibm.com, imunsie@au1.ibm.com,
manoj@linux.vnet.ibm.com
Subject: Re: [RESEND, v7, 2/2] cxl: Add set and get private data to context struct
Date: Tue, 28 Jun 2016 11:24:03 +0200 [thread overview]
Message-ID: <57724233.50709@linux.vnet.ibm.com> (raw)
In-Reply-To: <3rdzYL1XJgz9sCg@ozlabs.org>
Michael Ellerman wrote:
> On Fri, 2016-24-06 at 06:47:07 UTC, Philippe Bergheaud 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>
>>Signed-off-by: Philippe Bergheaud <felix@linux.vnet.ibm.com
>>Reviewed-by: Matthew R. Ochs <mrochs@linux.vnet.ibm.com>
>>Reviewed-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
>>---
>>No changes since v1. Added Matt Ochs reviewed-by tag.
>
>
> I'm not sure why this is RESEND ?
>
Sorry. That was because I made a typo in the title (I typed v6 instead of v7).
> Does this pair with [v7 1/2] ?
>
Yes it does.
> https://patchwork.ozlabs.org/patch/639644/
>
> It's a lot simpler if you just resend the whole series each time there is an
> update to any patch.
>
Got it, thank you.
Philippe
next prev parent reply other threads:[~2016-06-28 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 6:47 [RESEND v7,2/2] cxl: Add set and get private data to context struct Philippe Bergheaud
2016-06-28 8:08 ` Andrew Donnellan
2016-06-28 8:31 ` [RESEND, v7, 2/2] " Michael Ellerman
2016-06-28 9:24 ` Philippe Bergheaud [this message]
2016-06-30 12:36 ` Michael Ellerman
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=57724233.50709@linux.vnet.ibm.com \
--to=felix@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manoj@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=mrochs@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).