public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <christian@brauner.io>,
	Chandan Babu R <chandan.babu@oracle.com>,
	linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: xfs fixups for the fop_flags conversion
Date: Tue, 23 Apr 2024 20:33:04 -0700	[thread overview]
Message-ID: <20240424033304.GC360940@frogsfrogsfrogs> (raw)
In-Reply-To: <20240423124608.537794-1-hch@lst.de>

On Tue, Apr 23, 2024 at 02:46:05PM +0200, Christoph Hellwig wrote:
> Hi all,
> 
> this series against Christian's vfs.misc branch fixes up pointless
> harmless but pointless over-declaration of capabilities for XFS
> directories.
> 
> Christian: the first patch would make sense to just fold into the
> original fop_flags conversion if you're still rebasing the branch.

All three patches look good to me,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> 
>  xfs_file.c |   10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

  parent reply	other threads:[~2024-04-24  3:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 12:46 xfs fixups for the fop_flags conversion Christoph Hellwig
2024-04-23 12:46 ` [PATCH 1/3] xfs: fix overly long line in the file_operations Christoph Hellwig
2024-04-23 12:46 ` [PATCH 2/3] xfs: drop fop_flags for directories Christoph Hellwig
2024-04-23 12:46 ` [PATCH 3/3] xfs: don't call xfs_file_open from xfs_dir_open Christoph Hellwig
2024-04-24  3:33 ` Darrick J. Wong [this message]
2024-04-24 12:49 ` xfs fixups for the fop_flags conversion Christian Brauner

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=20240424033304.GC360940@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=christian@brauner.io \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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