From: Christian Brauner <brauner@kernel.org>
To: Chandan Babu R <chandan.babu@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: xfs fixups for the fop_flags conversion
Date: Wed, 24 Apr 2024 14:49:06 +0200 [thread overview]
Message-ID: <20240424-parameter-bekam-55dfd6f34ce6@brauner> (raw)
In-Reply-To: <20240423124608.537794-1-hch@lst.de>
On Tue, 23 Apr 2024 14:46:05 +0200, Christoph Hellwig wrote:
> 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.
>
> [...]
Thanks for the fixes! I didn't fold because it would rebase a lot of
other stuff which I'd like to avoid. :/
---
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/3] xfs: fix overly long line in the file_operations
https://git.kernel.org/vfs/vfs/c/19e048641bc6
[2/3] xfs: drop fop_flags for directories
https://git.kernel.org/vfs/vfs/c/f50805713a6e
[3/3] xfs: don't call xfs_file_open from xfs_dir_open
https://git.kernel.org/vfs/vfs/c/652efdeca5b1
prev parent reply other threads:[~2024-04-24 12:49 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 ` xfs fixups for the fop_flags conversion Darrick J. Wong
2024-04-24 12:49 ` Christian Brauner [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=20240424-parameter-bekam-55dfd6f34ce6@brauner \
--to=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--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