public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* linux-next: manual merge of the folio tree with the drm-intel tree
@ 2022-02-22  0:41 broonie
  2022-03-24  0:52 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: broonie @ 2022-02-22  0:41 UTC (permalink / raw)
  To: Matthew Wilcox
  Cc: Andrew Morton, Christoph Hellwig, Linux Kernel Mailing List,
	Linux Next Mailing List, Lucas De Marchi

Hi all,

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

  drivers/gpu/drm/drm_cache.c

between commit:

  7938f4218168a ("dma-buf-map: Rename to iosys-map")

from the drm-intel tree and commit:

  96160c2f78bd1 ("mm: don't include <linux/memremap.h> in <linux/mm.h>")

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 drivers/gpu/drm/drm_cache.c
index 4b0da6baff78e,50b8a088f763a..0000000000000
--- a/drivers/gpu/drm/drm_cache.c
+++ b/drivers/gpu/drm/drm_cache.c
@@@ -27,11 -27,11 +27,11 @@@
  /*
   * Authors: Thomas Hellström <thomas-at-tungstengraphics-dot-com>
   */
- 
 -#include <linux/dma-buf-map.h>
 +#include <linux/cc_platform.h>
  #include <linux/export.h>
  #include <linux/highmem.h>
 -#include <linux/cc_platform.h>
+ #include <linux/ioport.h>
 +#include <linux/iosys-map.h>
  #include <xen/xen.h>
  
  #include <drm/drm_cache.h>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-03-24  0:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-02-22  0:41 linux-next: manual merge of the folio tree with the drm-intel tree broonie
2022-03-24  0:52 ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox