From: Leonardo Bras <leonardo@linux.ibm.com>
To: Jens Axboe <axboe@kernel.dk>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] vmsplice.2: SPLICE_F_GIFT became no-op
Date: Wed, 18 Dec 2019 13:22:37 -0300 [thread overview]
Message-ID: <4171feef2b800a453543583e39a241f734cd317a.camel@linux.ibm.com> (raw)
In-Reply-To: <258fa69f-9eee-677b-e349-96197761dd3b@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
On Tue, 2019-12-17 at 18:13 -0700, Jens Axboe wrote:
> Sorry, better late than never?
No problem :)
> He's right, Nick Piggin removed that flag (and promised to reinstate it,
> but a decade later I'm not holding my breath).
Thanks for the feedback!
Best regards,
Leonardo Bras
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-12-18 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190801222417.14413-1-leonardo@linux.ibm.com>
2019-09-13 12:55 ` [PATCH] vmsplice.2: SPLICE_F_GIFT became no-op Michael Kerrisk (man-pages)
2019-11-14 18:56 ` Leonardo Bras
2019-12-17 21:12 ` Leonardo Bras
2019-12-18 1:13 ` Jens Axboe
2019-12-18 16:22 ` Leonardo Bras [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=4171feef2b800a453543583e39a241f734cd317a.camel@linux.ibm.com \
--to=leonardo@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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).