lkml.org 
[lkml]   [2022]   [Nov]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectlinux-next: manual merge of the kvm tree with the block tree
Hi all,

Today's linux-next merge of the kvm tree got a conflict in:

include/linux/mm.h

between commit:

4003f107fa2e ("mm: introduce FOLL_PCI_P2PDMA to gate getting PCI P2PDMA pages")

from the block tree and commit:

93c5c61d9e58 ("mm/gup: Add FOLL_INTERRUPTIBLE")

from the kvm 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.

--
Cheers,
Stephen Rothwell

idiff --cc include/linux/mm.h
index f0eab324102b,3c84f4e48cd7..000000000000
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@@ -2968,7 -2958,7 +2968,8 @@@ struct page *follow_page(struct vm_area
#define FOLL_SPLIT_PMD 0x20000 /* split huge pmd before returning */
#define FOLL_PIN 0x40000 /* pages must be released via unpin_user_page */
#define FOLL_FAST_ONLY 0x80000 /* gup_fast: prevent fall-back to slow gup */
-#define FOLL_INTERRUPTIBLE 0x100000 /* allow interrupts from generic signals */
+#define FOLL_PCI_P2PDMA 0x100000 /* allow returning PCI P2PDMA pages */
++#define FOLL_INTERRUPTIBLE 0x200000 /* allow interrupts from generic signals */

/*
* FOLL_PIN and FOLL_LONGTERM may be used in various combinations with each
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2022-12-01 01:15    [W:0.018 / U:0.776 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site