From: Michael Ellerman <mpe@ellerman.id.au>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: chandan@mykolab.com, Chandan Rajendra <chandan@linux.vnet.ibm.com>
Subject: Re: powerpc: Wire up copy_file_range() syscall
Date: Thu, 21 Jan 2016 16:34:07 +1100 (AEDT) [thread overview]
Message-ID: <20160121053407.EC92A140BF9@ozlabs.org> (raw)
In-Reply-To: <1452703822-29844-1-git-send-email-chandan@linux.vnet.ibm.com>
On Wed, 2016-13-01 at 16:50:22 UTC, Chandan Rajendra wrote:
> Test runs on a ppc64 BE guest succeeded.
>
> Signed-off-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/d7f9ee60a6ebc263861a1d8c06
cheers
prev parent reply other threads:[~2016-01-21 5:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 16:50 [PATCH] powerpc: Wire up copy_file_range() syscall Chandan Rajendra
2016-01-13 22:53 ` Michael Ellerman
2016-01-14 4:10 ` Chandan Rajendra
2016-01-21 5:34 ` Michael Ellerman [this message]
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=20160121053407.EC92A140BF9@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=chandan@linux.vnet.ibm.com \
--cc=chandan@mykolab.com \
--cc=linuxppc-dev@lists.ozlabs.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).