public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <brauner@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Pankaj Raghav <p.raghav@samsung.com>,
	Usama Arif <usamaarif642@gmail.com>
Subject: Re: linux-next: manual merge of the vfs-brauner tree with the mm tree
Date: Wed, 18 Sep 2024 10:34:12 +1000	[thread overview]
Message-ID: <20240918103412.0ce158d9@canb.auug.org.au> (raw)
In-Reply-To: <20240902112101.2728f045@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2572 bytes --]

Hi all,

On Mon, 2 Sep 2024 11:21:01 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the fs-next tree got a conflict in:
> 
>   include/linux/huge_mm.h
> 
> between commit:
> 
>   bc47772ebe8b ("mm: introduce a pageflag for partially mapped folios")
> 
> from the mm-unstable branch of the mm tree and commit:
> 
>   fd031210c9ce ("mm: split a folio in minimum folio order chunks")
> 
> from the vfs-brauner 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 include/linux/huge_mm.h
> index 0b0539f4ee1a,7c50aeed0522..000000000000
> --- a/include/linux/huge_mm.h
> +++ b/include/linux/huge_mm.h
> @@@ -326,14 -316,15 +328,15 @@@ unsigned long thp_get_unmapped_area_vmf
>   		unsigned long len, unsigned long pgoff, unsigned long flags,
>   		vm_flags_t vm_flags);
>   
>  -bool can_split_folio(struct folio *folio, int *pextra_pins);
>  +bool can_split_folio(struct folio *folio, int caller_pins, int *pextra_pins);
>   int split_huge_page_to_list_to_order(struct page *page, struct list_head *list,
>   		unsigned int new_order);
> + int split_folio_to_list(struct folio *folio, struct list_head *list);
>   static inline int split_huge_page(struct page *page)
>   {
> - 	return split_huge_page_to_list_to_order(page, NULL, 0);
> + 	return split_folio(page_folio(page));
>   }
>  -void deferred_split_folio(struct folio *folio);
>  +void deferred_split_folio(struct folio *folio, bool partially_mapped);
>   
>   void __split_huge_pmd(struct vm_area_struct *vma, pmd_t *pmd,
>   		unsigned long address, bool freeze, struct folio *folio);
> @@@ -502,7 -487,13 +505,13 @@@ static inline int split_huge_page(struc
>   {
>   	return 0;
>   }
> + 
> + static inline int split_folio_to_list(struct folio *folio, struct list_head *list)
> + {
> + 	return 0;
> + }
> + 
>  -static inline void deferred_split_folio(struct folio *folio) {}
>  +static inline void deferred_split_folio(struct folio *folio, bool partially_mapped) {}
>   #define split_huge_pmd(__vma, __pmd, __address)	\
>   	do { } while (0)
>   

This is now a conflict between the vfs-brauner tree and the mm-stable
tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2024-09-18  0:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  1:21 linux-next: manual merge of the vfs-brauner tree with the mm tree Stephen Rothwell
2024-09-02  9:18 ` Pankaj Raghav (Samsung)
2024-09-18  0:34 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-20 23:32 Stephen Rothwell
2024-03-11 21:56 ` Stephen Rothwell
2023-11-21 23:31 Stephen Rothwell
2024-01-08 21:00 ` Stephen Rothwell
2023-09-28  0:25 Stephen Rothwell
2023-10-30 22:30 ` Stephen Rothwell
2023-09-20 23:13 Stephen Rothwell
2023-07-14  0:24 Stephen Rothwell
2023-07-14  0:02 Stephen Rothwell
2023-05-24  0:06 Stephen Rothwell

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=20240918103412.0ce158d9@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=usamaarif642@gmail.com \
    /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