All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark yao <mark.yao-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
To: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Cc: David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [GIT PULL] drm/rockchip: convert to drm_mm
Date: Mon, 27 Feb 2017 10:20:28 +0800	[thread overview]
Message-ID: <58B38CEC.3020106@rock-chips.com> (raw)
In-Reply-To: <20170226204554.y3dqu52hzrgbv5rj-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>

On 2017年02月27日 04:45, Daniel Vetter wrote:
> On Thu, Feb 16, 2017 at 11:02:31AM +0800, Mark yao wrote:
>> Hi Dave
>>
>> After convert to drm_mm, rockchip arm64 platform can works with iommu, like
>> rk3399. it's import patches for rockchip arm64 platform
>>
>> And these patches already have full reviewed, I hope these patches can be
>> landed.
>>   
>> Best regards
>>
>> The following changes since commit 13f62f54d174d3417c3caaafedf5e22a0a03e442:
>>
>>    Merge branch 'drm-next-4.11' of git://people.freedesktop.org/~agd5f/linux
>> into drm-next (2017-02-10 10:13:30 +1000)
>>
>> are available in the git repository at:
>>
>>
>>    https://github.com/markyzq/kernel-drm-rockchip.git
>> drm-rockchip-next-2017-02-16
>>
>> for you to fetch changes up to 1aa5ca6e3ec63aa5815d78646748e88a7ceb1c8e:
>>
>>    drm/rockchip: Use common IOMMU API to attach devices (2017-02-15 08:52:13
>> +0800)
>>
>> ----------------------------------------------------------------
>> Shunqian Zheng (1):
>>        drm/rockchip: Use common IOMMU API to attach devices
>>
>> Tomasz Figa (1):
>>        drm/rockchip: Do not use DMA mapping API if attached to IOMMU domain
> I thought we've moved rockchip into drm-misc ...?

Sorry, I'm not clear understand how the drm-misc maintain before, later 
patches would go through drm-misc

> Can you and Sean Paul please talk and figure out how exactly you want to
> maintain this driver?

Move drm/rockchip into drm-misc is good, Thanks Sean Paul's work.
I'm learning how to maintain drm/rockchip with drm-misc.

But I'm not understand drm-misc's step, I'm confused that:  do I need to 
pick up patches to drm-misc by myself?
or I just give a ACK on patches, and then Sean or other drm-misc's guys 
will pick patches up to drm-misc?

Thanks.
> The current situation where we have stuff going in
> independently through different maintainers is not great at all. If you
> can't get agreement, we'll just make you agree by arbitrarily rolling the
> dice or something silly like that :-)
> -Daniel

-- 
Ｍark Yao



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

      parent reply	other threads:[~2017-02-27  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16  3:02 [GIT PULL] drm/rockchip: convert to drm_mm Mark yao
     [not found] ` <58A51647.2040003-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-02-26 20:45   ` Daniel Vetter
     [not found]     ` <20170226204554.y3dqu52hzrgbv5rj-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2017-02-27  2:20       ` Mark yao [this message]

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=58B38CEC.3020106@rock-chips.com \
    --to=mark.yao-tnx95d0mmh7dzftrwevzcw@public.gmane.org \
    --cc=airlied-cv59FeDIM0c@public.gmane.org \
    --cc=daniel-/w4YWyX8dFk@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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.