From: Matthew Wilcox <willy@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-xfs@vger.kernel.org, linux-afs@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] afs: Split afs_pagecache_valid() out of afs_validate()
Date: Thu, 9 Feb 2023 14:56:59 +0000 [thread overview]
Message-ID: <Y+UJu6PLCHYXl5il@casper.infradead.org> (raw)
In-Reply-To: <684134.1675952905@warthog.procyon.org.uk>
On Thu, Feb 09, 2023 at 02:28:25PM +0000, David Howells wrote:
> Matthew Wilcox (Oracle) <willy@infradead.org> wrote:
>
> > extern int afs_getattr(struct mnt_idmap *idmap, const struct path *,
> > struct kstat *, u32, unsigned int);
> > extern int afs_setattr(struct mnt_idmap *idmap, struct dentry *, struct iattr *);
>
> This doesn't apply to linus/master. I'm guessing it's based on something
> else?
next-20230203. I'm guessing it's "fs: port xattr to mnt_idmap" that's
causing merge conflicts for you?
next prev parent reply other threads:[~2023-02-09 14:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 14:53 [PATCH 0/3] Prevent ->map_pages from sleeping Matthew Wilcox (Oracle)
2023-02-08 14:53 ` [PATCH 1/3] xfs: Remove xfs_filemap_map_pages() wrapper Matthew Wilcox (Oracle)
2023-02-08 16:39 ` Darrick J. Wong
2023-02-08 17:12 ` Matthew Wilcox
2023-02-08 21:53 ` Dave Chinner
2023-02-09 2:44 ` Matthew Wilcox
2023-02-09 21:53 ` Dave Chinner
2023-02-09 22:34 ` Matthew Wilcox
2023-02-09 23:59 ` Dave Chinner
2023-02-08 14:53 ` [PATCH 2/3] afs: Split afs_pagecache_valid() out of afs_validate() Matthew Wilcox (Oracle)
2023-02-09 14:28 ` David Howells
2023-02-09 14:56 ` Matthew Wilcox [this message]
2023-02-09 14:49 ` David Howells
2023-02-08 14:53 ` [PATCH 3/3] mm: Hold the RCU read lock over calls to ->map_pages Matthew Wilcox (Oracle)
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=Y+UJu6PLCHYXl5il@casper.infradead.org \
--to=willy@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.