Linux-Next Archive on
 help / color / Atom feed
* linux-next: manual merge of the amdgpu-fixes tree with the drm-fixes tree
@ 2019-08-08 21:55 Stephen Rothwell
  0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2019-08-08 21:55 UTC (permalink / raw)
  To: Alex Deucher, Dave Airlie, DRI
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Joseph Greathouse

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

Hi all,

Today's linux-next merge of the amdgpu-fixes tree got conflicts in:


between commit:

  4b3e30ed3ec7 ("Revert "drm/amdkfd: New IOCTL to allocate queue GWS"")

from the drm-fixes tree and commit:

  7e51b56cd5b8 ("drm/amdkfd: Remove GPU ID in GWS queue creation")

from the amdgpu-fixes tree.

I fixed it up (I just used the former) 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.

Stephen Rothwell

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-08 21:55 linux-next: manual merge of the amdgpu-fixes tree with the drm-fixes tree Stephen Rothwell

Linux-Next Archive on

Archives are clonable:
	git clone --mirror linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ \
	public-inbox-index linux-next

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox