linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Daniel Vetter" <daniel@ffwll.ch>,
	"Christian König" <christian.koenig@amd.com>
Cc: "moderated list:DMA BUFFER SHARING FRAMEWORK"
	<linaro-mm-sig@lists.linaro.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	"open list:DMA BUFFER SHARING FRAMEWORK"
	<linux-media@vger.kernel.org>
Subject: Re: [PATCH 2/5] dma-buf: remove kmap_atomic interface
Date: Wed, 20 Jun 2018 16:04:20 +0200	[thread overview]
Message-ID: <5d337ffc-6c4c-dafb-abb2-151d9d4aeaea@gmail.com> (raw)
In-Reply-To: <CAKMK7uHHZn=H6px-yiXy7tVmmQy6GHrwGtG+B7or1ThsrriFDA@mail.gmail.com>

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

Am 20.06.2018 um 14:52 schrieb Daniel Vetter:
> On Wed, Jun 20, 2018 at 2:46 PM, Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> [SNIP]
>>> Go ahead, that's the point of commit rights. dim might complain if you
>>> cherry picked them and didn't pick them up using dim apply though ...
>>
>> I've fixed up the Link tags, but when I try "dim push-branch drm-misc-next"
>> I only get the error message "error: dst ref refs/heads/drm-misc-next
>> receives from more than one src."
>>
>> Any idea what is going wrong here?
> Sounds like multiple upstreams for your local drm-misc-next branch,
> and git then can't decide which one to pick. If you delete the branch
> and create it using dim checkout drm-misc-next this shouldn't happen.
> We're trying to fit into existing check-outs and branches, but if you
> set things up slightly different than dim would have you're off script
> and there's limited support for that.
>
> Alternative check out your .git/config and remove the other upstreams.
> Or attach your git config if this isn't the issue (I'm just doing some
> guessing here).

I've tried to delete my drm-misc-next branch and recreate it, but that 
doesn't seem to help.

Attached is my .git/config, but at least on first glance it looks ok as 
well.

Any ideas?

Thanks,
Christian.

> -Daniel
>
>


[-- Attachment #2: config --]
[-- Type: text/plain, Size: 1499 bytes --]

[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
[remote "origin"]
	url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
	remote = origin
	merge = refs/heads/master
[remote "drm-tip"]
	url = ssh://git.freedesktop.org/git/drm-tip
	fetch = +refs/heads/*:refs/remotes/drm-tip/*
[branch "maintainer-tools"]
	remote = drm-tip
	merge = refs/heads/maintainer-tools
[branch "rerere-cache"]
	remote = drm-tip
	merge = refs/heads/rerere-cache
[branch "drm-tip"]
	remote = drm-tip
	merge = refs/heads/drm-tip
[remote "airlied"]
	url = git://people.freedesktop.org/~airlied/linux
	fetch = +refs/heads/*:refs/remotes/airlied/*
[remote "sound"]
	url = git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
	fetch = +refs/heads/*:refs/remotes/sound/*
[remote "drm-intel"]
	url = ssh://git.freedesktop.org/git/drm/drm-intel
	fetch = +refs/heads/*:refs/remotes/drm-intel/*
[remote "drm-amd"]
	url = ssh://git.freedesktop.org/git/drm/drm-amd
	fetch = +refs/heads/*:refs/remotes/drm-amd/*
[remote "drm"]
	url = ssh://git.freedesktop.org/git/drm/drm
	fetch = +refs/heads/*:refs/remotes/drm/*
[remote "drm-misc"]
	url = ssh://git.freedesktop.org/git/drm/drm-misc
	fetch = +refs/heads/*:refs/remotes/drm-misc/*
[remote "baker"]
	url = ssh://baker.local/usr/src/linux
	fetch = +refs/heads/*:refs/remotes/baker/*
[branch "drm-misc-next"]
	remote = drm-misc
	merge = refs/heads/drm-misc-next

  reply	other threads:[~2018-06-20 14:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 12:00 [PATCH 1/5] dma_buf: remove device parameter from attach callback Christian König
2018-06-01 12:00 ` [PATCH 2/5] dma-buf: remove kmap_atomic interface Christian König
2018-06-18  8:18   ` Daniel Vetter
2018-06-19 14:47     ` Christian König
2018-06-19 15:35       ` Daniel Vetter
2018-06-20 12:46         ` Christian König
2018-06-20 12:52           ` Daniel Vetter
2018-06-20 14:04             ` Christian König [this message]
2018-06-20 14:21               ` Christian König
2018-06-21  6:26                 ` Daniel Vetter
2018-06-21  6:30                   ` Daniel Vetter
2018-06-21 10:59                     ` Christian König
2018-06-20  6:10       ` Sumit Semwal
2018-06-20  6:22         ` Christian König
2018-06-01 12:00 ` [PATCH 3/5] dma-buf: lock the reservation object during (un)map_dma_buf Christian König
2018-06-18  8:22   ` Daniel Vetter
2018-06-18 12:43     ` Christian König
2018-06-01 12:00 ` [PATCH 4/5] dma-buf: add dma_buf_(un)map_attachment_locked variants Christian König
2018-06-18  8:27   ` Daniel Vetter
2018-06-01 12:00 ` [PATCH 5/5] drm/amdgpu: add independent DMA-buf export v3 Christian König
2018-06-18  8:28   ` Daniel Vetter
2018-06-22 13:39     ` Christian König
2018-06-25  7:46       ` Daniel Vetter
2018-06-01 12:11 ` [PATCH 1/5] dma_buf: remove device parameter from attach callback Christian König
2018-06-01 14:02   ` Michel Dänzer
2018-06-01 15:17     ` Christian König
2018-06-01 15:30       ` Michel Dänzer
2018-06-06 11:24 ` Christian König
2018-06-18  8:14 ` Daniel Vetter

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=5d337ffc-6c4c-dafb-abb2-151d9d4aeaea@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).