From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>,
Ilya Dryomov <idryomov@gmail.com>, Yan Zheng <zyan@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [git pull] vfs.git
Date: Fri, 11 Nov 2016 09:25:01 -0800 [thread overview]
Message-ID: <CA+55aFwjKs6gR8hduBr5sPHRqsww1sjXdMP7AvZNF4Jz1HRYXw@mail.gmail.com> (raw)
In-Reply-To: <20161111060515.GQ19539@ZenIV.linux.org.uk>
On Thu, Nov 10, 2016 at 10:05 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> Christoph's and Jan's aio fixes, fixup for generic_file_splice_read
> (removal of pointless detritus that actually breaks it when used for gfs2
> ->splice_read()) and fixup for generic_file_read_iter() interaction with
> ITER_PIPE destinations.
Hmm. I also just pulled the Ceph update that has commit 8a8d56176635
("ceph: use default file splice read callback"). I _think_ this splice
fix makes that ceph change unnecessary. But testing is always good.
Ilya? Can you double-check the current -git tree (well, what I *will*
push out soon after it has passed my build tests)?
Because I think Ceph can go back to using generic_file_splice_read again.
Linus
next prev parent reply other threads:[~2016-11-11 17:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 6:05 [git pull] vfs.git Al Viro
2016-11-11 17:25 ` Linus Torvalds [this message]
2016-11-11 18:06 ` Ilya Dryomov
2016-11-12 3:36 ` Yan, Zheng
-- strict thread matches above, loose matches on Subject: below --
2016-11-17 5:55 Al Viro
2016-10-11 3:07 Al Viro
2016-05-16 3:32 Al Viro
2016-05-16 15:43 ` Linus Torvalds
2016-05-17 6:27 ` Al Viro
2016-05-17 18:27 ` Linus Torvalds
2016-05-17 20:11 ` Al Viro
2016-03-20 1:44 Al Viro
2016-03-20 1:55 ` Linus Torvalds
2016-03-20 1:59 ` Al Viro
2015-04-24 20:40 Al Viro
2014-12-10 19:13 [GIT PULL] vfs.git Al Viro
2014-12-11 16:18 ` Miklos Szeredi
2014-12-11 18:06 ` Al Viro
2014-12-11 18:34 ` Al Viro
2014-11-05 13:57 [git pull] vfs.git Al Viro
2014-11-02 5:58 Al Viro
2014-10-26 3:04 Al Viro
2014-05-28 6:38 Al Viro
2014-04-12 12:40 Al Viro
2014-04-13 18:53 ` Geert Uytterhoeven
2013-11-11 16:30 Al Viro
2013-11-13 14:52 ` J. Bruce Fields
2013-06-15 3:34 Al Viro
2012-12-21 0:21 Al Viro
2012-06-01 16:56 Al Viro
2012-06-01 17:38 ` Linus Torvalds
2012-06-01 17:38 ` Linus Torvalds
2012-06-01 17:48 ` Al Viro
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=CA+55aFwjKs6gR8hduBr5sPHRqsww1sjXdMP7AvZNF4Jz1HRYXw@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=idryomov@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zyan@redhat.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.