From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Paul Subject: Re: [PATCH v3 1/5] drm/rockchip: sort registers define by chip's number Date: Thu, 25 Aug 2016 13:15:26 -0400 Message-ID: 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> <57BE5727.8070100@rock-chips.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1490462773==" Return-path: In-Reply-To: <57BE5727.8070100@rock-chips.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Mark yao Cc: Linux ARM Kernel , linux-rockchip@lists.infradead.org, Linux Kernel Mailing List , dri-devel , Tomasz Figa List-Id: linux-rockchip.vger.kernel.org --===============1490462773== Content-Type: multipart/alternative; boundary=001a113fcf907e86f0053ae88c81 --001a113fcf907e86f0053ae88c81 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Aug 24, 2016 at 10:25 PM, Mark yao wrote: > On 2016=E5=B9=B408=E6=9C=8823=E6=97=A5 21:13, Sean Paul wrote: > >> On Mon, Aug 22, 2016 at 8:40 PM, Mark yao >> wrote: >> >>> On 2016=E5=B9=B408=E6=9C=8823=E6=97=A5 04:30, Sean Paul wrote: >>> >>>> On Thu, Aug 18, 2016 at 6:02 AM, Mark yao >>>> wrote: >>>> >>>>> On 2016=E5=B9=B408=E6=9C=8818=E6=97=A5 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 t= o >>>>> 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. > > You should probably just rebase your downstream kernel on top of my branch here: https://cgit.freedesktop.org/~seanpaul/dogwood/log/?h=3Dfor-next Sean Thanks. > > > >>>> Thanks. >>>>> >>>>> -- >>>>> =EF=BC=ADark Yao >>>>> >>>>> >>>>> >>>> >>> -- >>> =EF=BC=ADark Yao >>> >>> >>> >> >> > > -- > =EF=BC=ADark Yao > > > --001a113fcf907e86f0053ae88c81 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Aug 24, 2016 at 10:25 PM, Mark yao <mark.yao@rock-chips.com> wrote:
On 2016=E5=B9=B408=E6=9C=8823=E6=97=A5 21:13, Sean Paul wrote:
On Mon, Aug 22, 2016 at 8:40 PM, Mark yao <mark.yao@rock= -chips.com> wrote:
On 2016=E5=B9=B408=E6=9C=8823=E6=97=A5 04:30, Sean Paul wrote:
On Thu, Aug 18, 2016 at 6:02 AM, Mark yao <mark.yao@rock= -chips.com> wrote:
On 2016=E5=B9=B408=E6=9C=8818=E6=97=A5 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,=C2=A0 Sean's p= atches
is
old version.

I just want to fast forward, don't want to send two version drivers to<= br> 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 los= t
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.


You should probably just rebase your d= ownstream kernel on top of my branch here: https://cgit.freedesktop.org/~= seanpaul/dogwood/log/?h=3Dfor-next=C2=A0
=C2=A0
Sea= n


Thanks.



Thanks.

--
=EF=BC=ADark Yao




--
=EF=BC=ADark Yao






--
=EF=BC=ADark Yao



--001a113fcf907e86f0053ae88c81-- --===============1490462773== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1490462773==--