cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 11/11] fuse: drop redundant arguments to fuse_perform_write
Date: Tue, 30 May 2023 09:04:28 +0200	[thread overview]
Message-ID: <9d7b392d-727b-1744-90d0-526b61dcfccf@suse.de> (raw)
In-Reply-To: <20230524063810.1595778-12-hch@lst.de>

On 5/24/23 08:38, Christoph Hellwig wrote:
> pos is always equal to iocb->ki_pos, and mapping is always equal to
> iocb->ki_filp->f_mapping.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> ---
>   fs/fuse/file.c | 11 +++++------
>   1 file changed, 5 insertions(+), 6 deletions(-)
> 
Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare at suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 N?rnberg
HRB 36809 (AG N?rnberg), Gesch?ftsf?hrer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman


      parent reply	other threads:[~2023-05-30  7:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  6:37 [Cluster-devel] cleanup the filemap / direct I/O interaction v2 Christoph Hellwig
2023-05-24  6:38 ` [Cluster-devel] [PATCH 01/11] backing_dev: remove current->backing_dev_info Christoph Hellwig
2023-05-24 14:50   ` Darrick J. Wong
2023-05-30  6:56   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 02/11] iomap: update ki_pos a little later in iomap_dio_complete Christoph Hellwig
2023-05-30  6:57   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 03/11] filemap: update ki_pos in generic_perform_write Christoph Hellwig
2023-05-30  6:57   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 04/11] filemap: add a kiocb_write_and_wait helper Christoph Hellwig
2023-05-30  6:58   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 05/11] filemap: add a kiocb_invalidate_pages helper Christoph Hellwig
2023-05-30  6:59   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 06/11] filemap: add a kiocb_invalidate_post_direct_write helper Christoph Hellwig
2023-05-30  6:59   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 07/11] iomap: update ki_pos in iomap_file_buffered_write Christoph Hellwig
2023-05-25 16:02   ` Andreas Gruenbacher
2023-05-30  7:00   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 08/11] iomap: use kiocb_write_and_wait and kiocb_invalidate_pages Christoph Hellwig
2023-05-30  7:02   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 09/11] fs: factor out a direct_write_fallback helper Christoph Hellwig
2023-05-24  7:00   ` Miklos Szeredi
2023-05-25 10:05     ` Christoph Hellwig
2023-05-30  7:03   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 10/11] fuse: update ki_pos in fuse_perform_write Christoph Hellwig
2023-05-24  7:07   ` Miklos Szeredi
2023-05-25 10:09     ` Christoph Hellwig
2023-05-30  7:04   ` Hannes Reinecke
2023-05-24  6:38 ` [Cluster-devel] [PATCH 11/11] fuse: drop redundant arguments to fuse_perform_write Christoph Hellwig
2023-05-24  7:09   ` Miklos Szeredi
2023-05-30  7:04   ` Hannes Reinecke [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=9d7b392d-727b-1744-90d0-526b61dcfccf@suse.de \
    --to=hare@suse.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).