From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754973AbcHYEcU (ORCPT ); Thu, 25 Aug 2016 00:32:20 -0400 Received: from regular1.263xmail.com ([211.150.99.132]:39596 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752746AbcHYEcN (ORCPT ); Thu, 25 Aug 2016 00:32:13 -0400 X-263anti-spam: KSV:0;BIG:0;ABS:1;DNS:0;ATT:0;SPF:S; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ABS-CHECKED: 1 X-SKE-CHECKED: 1 X-ADDR-CHECKED: 0 X-RL-SENDER: mark.yao@rock-chips.com X-FST-TO: linux-arm-kernel@lists.infradead.org X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: mark.yao@rock-chips.com X-UNIQUE-TAG: <8e1dec0351b586263b1447380a974249> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [PATCH v3 1/5] drm/rockchip: sort registers define by chip's number To: Sean Paul References: <1471454452-2151-1-git-send-email-seanpaul@chromium.org> <57B57AFE.2030706@rock-chips.com> <20160818091141.GZ6232@phenom.ffwll.local> <57B587C0.5050007@rock-chips.com> <57BB9B87.2040406@rock-chips.com> Cc: Tomasz Figa , dri-devel , linux-rockchip@lists.infradead.org, Linux Kernel Mailing List , Linux ARM Kernel From: Mark yao Message-ID: <57BE5727.8070100@rock-chips.com> Date: Thu, 25 Aug 2016 10:25:43 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016年08月23日 21:13, Sean Paul wrote: > On Mon, Aug 22, 2016 at 8:40 PM, Mark yao wrote: >> On 2016年08月23日 04:30, Sean Paul wrote: >>> On Thu, Aug 18, 2016 at 6:02 AM, Mark yao wrote: >>>> On 2016年08月18日 17:11, Daniel Vetter wrote: >>>>> On Thu, Aug 18, 2016 at 05:08:14PM +0800, Mark yao wrote: >>>>>>> Hi Sean >>>>>>> >>>>>>> Thanks for send v3 patch for rk3399 vop support. >>>>>>> >>>>>>> But sorry for that, I had changed my mind, those patches are >>>>>>> deprecated, >>>>>>> I have new rk3399 patch on my downstream kernel, I will upstream soon. >>>>> Wut? Imo merge Sean's patch here, and then rebase your downstream >>>>> patches >>>>> on top of it. That you have a downstream tree which is out of sync with >>>>> upstream shouldn't be a reason to stall upstream development. >>>>> -Daniel >>>>> >>>> Yeah, Sorry for that. >>>> >>>> In fact, on my downstream kernel, also have those patches, my new rk3399 >>>> patches are based on them, >>>> but the new rk3399 patches will cover the those patches, Sean's patches >>>> is >>>> old version. >>>> >>>> I just want to fast forward, don't want to send two version drivers to >>>> upstream. >>>> but if you and Dave feel ok for that, I have no problem:-) . >>>> >>>> merged Sean's patches and then apply new version patches. >>>> >>> Ok, so can I get a review/ack for these revised patches then? >>> Something is better than nothing, and there's a bunch of stuff that >>> depends on these changes. >>> >>> Sean >> Yes, But I miss your [PATCH v3 0/5] and [PATCH v3 4/5]. do you mean the lost >> patches use v2 version? >> > Yes, v2 4/5 was reviewed as-is, so I just applied it. > > Sean Applied this series to my drm-next. Thanks. >>> >>>> Thanks. >>>> >>>> -- >>>> Ｍark Yao >>>> >>>> >>> >> >> -- >> Ｍark Yao >> >> > > -- Ｍark Yao