Re: [PATCH 2/3] btrfs: Initialize inode->i_op once in btrfs_symlink

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 2/3] btrfs: Initialize inode->i_op once in btrfs_symlink
From: David Sterba <dsterba@xxxxxxx>
Date: Wed, 27 Feb 2019 16:39:32 +0100
Cc: linux-btrfs@xxxxxxxxxxxxxxx, Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
In-reply-to: <20190225190744.21664-2-rgoldwyn@suse.de>
Mail-followup-to: dsterba@xxxxxxx, Goldwyn Rodrigues <rgoldwyn@xxxxxxx>, linux-btrfs@xxxxxxxxxxxxxxx, Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
References: <20190225190744.21664-1-rgoldwyn@suse.de> <20190225190744.21664-2-rgoldwyn@suse.de>
Reply-to: dsterba@xxxxxxx
User-agent: Mutt/1.5.23.1 (2014-03-12)

On Mon, Feb 25, 2019 at 01:07:43PM -0600, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
> 
> inode->i_op is initialized multiple times. Perform it once.
> 
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>

Leftover from 4779cc04248deff6

Reviewed-by: David Sterba <dsterba@xxxxxxxx>

References:
- [PATCH 1/3] btrfs: Initialize btrfs_io_ctl instead of memsetting it
  - From: Goldwyn Rodrigues
- [PATCH 2/3] btrfs: Initialize inode->i_op once in btrfs_symlink
  - From: Goldwyn Rodrigues

Prev by Date: Re: [PATCH 3/3] btrfs: Perform locking/unlocking in btrfs_remap_file_range()
Next by Date: Re: [PATCH 1/3] btrfs: Initialize btrfs_io_ctl instead of memsetting it
Previous by thread: [PATCH 2/3] btrfs: Initialize inode->i_op once in btrfs_symlink
Next by thread: [PATCH 3/3] btrfs: Perform locking/unlocking in btrfs_remap_file_range()
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux