From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Howells <dhowells@redhat•com>
Cc: Matthew Wilcox <willy@infradead•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: manual merge of the folio tree with the fscache tree
Date: Thu, 24 Mar 2022 10:53:17 +1100 [thread overview]
Message-ID: <20220324105317.67a81b0e@canb.auug.org.au> (raw)
In-Reply-To: <20220315202512.62f54300@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
Hi all,
On Tue, 15 Mar 2022 20:25:12 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the folio tree got a conflict in:
>
> fs/9p/vfs_addr.c
>
> between commit:
>
> 0c31679cf2c0 ("netfs: Add a netfs inode context")
>
> from the fscache tree and commit:
>
> 09f7fc259e5d ("fscache: Convert fscache_set_page_dirty() to fscache_dirty_folio()")
>
> from the folio tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
>
> diff --cc fs/9p/vfs_addr.c
> index ed06f3c34e98,76956c9d2af9..000000000000
> --- a/fs/9p/vfs_addr.c
> +++ b/fs/9p/vfs_addr.c
> @@@ -353,9 -370,9 +336,9 @@@ static bool v9fs_dirty_folio(struct add
> #endif
>
> const struct address_space_operations v9fs_addr_operations = {
> - .readpage = v9fs_vfs_readpage,
> - .readahead = v9fs_vfs_readahead,
> + .readpage = netfs_readpage,
> + .readahead = netfs_readahead,
> - .set_page_dirty = v9fs_set_page_dirty,
> + .dirty_folio = v9fs_dirty_folio,
> .writepage = v9fs_vfs_writepage,
> .write_begin = v9fs_write_begin,
> .write_end = v9fs_write_end,
This is now a conflict between the fscache tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-23 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 9:25 linux-next: manual merge of the folio tree with the fscache tree Stephen Rothwell
2022-03-23 23:53 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-15 9:28 Stephen Rothwell
2022-03-23 23:54 ` Stephen Rothwell
2021-09-21 3:54 Stephen Rothwell
2021-11-01 22:07 ` Stephen Rothwell
2021-11-02 7:04 ` David Howells
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=20220324105317.67a81b0e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=willy@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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