All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Colin Ian King <colin.king@canonical.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the drm-misc tree with the origin tree
Date: Mon, 8 Nov 2021 09:31:14 +1100	[thread overview]
Message-ID: <20211108093114.12dde19b@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c

between commit:

  9ae807f0ec6a ("drm/amdgpu: clean up inconsistent indenting")

from the origin tree and commit:

  0d979509539e ("drm/ttm: remove ttm_bo_vm_insert_huge()")

from the drm-misc 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

diff --cc drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
index a573424a6e0b,a1e63ba4c54a..000000000000
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
@@@ -60,9 -60,10 +60,9 @@@ static vm_fault_t amdgpu_gem_fault(stru
  			goto unlock;
  		}
  
 -		 ret = ttm_bo_vm_fault_reserved(vmf, vmf->vma->vm_page_prot,
 -						TTM_BO_VM_NUM_PREFAULT);
 -
 -		 drm_dev_exit(idx);
 +		ret = ttm_bo_vm_fault_reserved(vmf, vmf->vma->vm_page_prot,
- 					       TTM_BO_VM_NUM_PREFAULT, 1);
++					       TTM_BO_VM_NUM_PREFAULT);
 +		drm_dev_exit(idx);
  	} else {
  		ret = ttm_bo_vm_dummy_page(vmf, vmf->vma->vm_page_prot);
  	}

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

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Colin Ian King <colin.king@canonical.com>
Subject: linux-next: manual merge of the drm-misc tree with the origin tree
Date: Mon, 8 Nov 2021 09:31:14 +1100	[thread overview]
Message-ID: <20211108093114.12dde19b@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c

between commit:

  9ae807f0ec6a ("drm/amdgpu: clean up inconsistent indenting")

from the origin tree and commit:

  0d979509539e ("drm/ttm: remove ttm_bo_vm_insert_huge()")

from the drm-misc 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

diff --cc drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
index a573424a6e0b,a1e63ba4c54a..000000000000
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
@@@ -60,9 -60,10 +60,9 @@@ static vm_fault_t amdgpu_gem_fault(stru
  			goto unlock;
  		}
  
 -		 ret = ttm_bo_vm_fault_reserved(vmf, vmf->vma->vm_page_prot,
 -						TTM_BO_VM_NUM_PREFAULT);
 -
 -		 drm_dev_exit(idx);
 +		ret = ttm_bo_vm_fault_reserved(vmf, vmf->vma->vm_page_prot,
- 					       TTM_BO_VM_NUM_PREFAULT, 1);
++					       TTM_BO_VM_NUM_PREFAULT);
 +		drm_dev_exit(idx);
  	} else {
  		ret = ttm_bo_vm_dummy_page(vmf, vmf->vma->vm_page_prot);
  	}

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

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Colin Ian King <colin.king@canonical.com>
Subject: [Intel-gfx] linux-next: manual merge of the drm-misc tree with the origin tree
Date: Mon, 8 Nov 2021 09:31:14 +1100	[thread overview]
Message-ID: <20211108093114.12dde19b@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c

between commit:

  9ae807f0ec6a ("drm/amdgpu: clean up inconsistent indenting")

from the origin tree and commit:

  0d979509539e ("drm/ttm: remove ttm_bo_vm_insert_huge()")

from the drm-misc 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

diff --cc drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
index a573424a6e0b,a1e63ba4c54a..000000000000
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
@@@ -60,9 -60,10 +60,9 @@@ static vm_fault_t amdgpu_gem_fault(stru
  			goto unlock;
  		}
  
 -		 ret = ttm_bo_vm_fault_reserved(vmf, vmf->vma->vm_page_prot,
 -						TTM_BO_VM_NUM_PREFAULT);
 -
 -		 drm_dev_exit(idx);
 +		ret = ttm_bo_vm_fault_reserved(vmf, vmf->vma->vm_page_prot,
- 					       TTM_BO_VM_NUM_PREFAULT, 1);
++					       TTM_BO_VM_NUM_PREFAULT);
 +		drm_dev_exit(idx);
  	} else {
  		ret = ttm_bo_vm_dummy_page(vmf, vmf->vma->vm_page_prot);
  	}

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

             reply	other threads:[~2021-11-07 22:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 22:31 Stephen Rothwell [this message]
2021-11-07 22:31 ` [Intel-gfx] linux-next: manual merge of the drm-misc tree with the origin tree Stephen Rothwell
2021-11-07 22:31 ` Stephen Rothwell
2022-11-15 23:57 Stephen Rothwell
2022-11-15 23:57 ` Stephen Rothwell
2022-11-17 17:29 ` Nathan Chancellor
2022-11-17 17:29   ` Nathan Chancellor
2022-11-17 22:06   ` Stephen Rothwell
2022-11-17 22:06     ` Stephen Rothwell
2022-11-18  0:01     ` Nathan Chancellor
2022-11-18  0:01       ` Nathan Chancellor
2022-11-18  9:20       ` Maxime Ripard
2022-11-18  9:20         ` Maxime Ripard

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=20211108093114.12dde19b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alexander.deucher@amd.com \
    --cc=colin.king@canonical.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.