From: David Howells <dhowells@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: dhowells@redhat.com, Christian Brauner <brauner@kernel.org>,
Jan Kara <jack@suse.cz>, Jeff Layton <jlayton@kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Miklos Szeredi <miklos@szeredi.hu>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] splice: return type ssize_t from all helpers
Date: Tue, 12 Dec 2023 15:22:31 +0000 [thread overview]
Message-ID: <3138449.1702394551@warthog.procyon.org.uk> (raw)
In-Reply-To: <20231212094440.250945-2-amir73il@gmail.com>
Barring Jan's nit,
Reviewed-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2023-12-12 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 9:44 [PATCH v3 0/5] Prepare for fsnotify pre-content permission events Amir Goldstein
2023-12-12 9:44 ` [PATCH v3 1/5] splice: return type ssize_t from all helpers Amir Goldstein
2023-12-12 14:19 ` Jan Kara
2023-12-12 15:20 ` Christian Brauner
2023-12-12 9:44 ` [PATCH v3 2/5] fs: use splice_copy_file_range() inline helper Amir Goldstein
2023-12-12 9:44 ` [PATCH v3 3/5] fsnotify: split fsnotify_perm() into two hooks Amir Goldstein
2023-12-12 9:44 ` [PATCH v3 4/5] fsnotify: assert that file_start_write() is not held in permission hooks Amir Goldstein
2023-12-12 9:44 ` [PATCH v3 5/5] fsnotify: optionally pass access range in file " Amir Goldstein
2023-12-12 13:34 ` [PATCH v3 0/5] Prepare for fsnotify pre-content permission events Christian Brauner
2023-12-12 15:22 ` David Howells [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=3138449.1702394551@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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.