From: Mark yao <mark.yao@rock-chips.com> To: Sean Paul <seanpaul@chromium.org> Cc: Tomasz Figa <tfiga@chromium.org>, dri-devel <dri-devel@lists.freedesktop.org>, linux-rockchip@lists.infradead.org, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux ARM Kernel <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v3 1/5] drm/rockchip: sort registers define by chip's number Date: Tue, 23 Aug 2016 08:40:39 +0800 [thread overview] Message-ID: <57BB9B87.2040406@rock-chips.com> (raw) In-Reply-To: <CAOw6vbJdBwUdg5Qww-autFH=HvvaM-uac7-mN+Ja7PEDiPoPnw@mail.gmail.com> On 2016年08月23日 04:30, Sean Paul wrote: > On Thu, Aug 18, 2016 at 6:02 AM, Mark yao <mark.yao@rock-chips.com> 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? > > >> Thanks. >> >> -- >> Mark Yao >> >> > > -- Mark Yao
WARNING: multiple messages have this Message-ID (diff)
From: mark.yao@rock-chips.com (Mark yao) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 1/5] drm/rockchip: sort registers define by chip's number Date: Tue, 23 Aug 2016 08:40:39 +0800 [thread overview] Message-ID: <57BB9B87.2040406@rock-chips.com> (raw) In-Reply-To: <CAOw6vbJdBwUdg5Qww-autFH=HvvaM-uac7-mN+Ja7PEDiPoPnw@mail.gmail.com> On 2016?08?23? 04:30, Sean Paul wrote: > On Thu, Aug 18, 2016 at 6:02 AM, Mark yao <mark.yao@rock-chips.com> 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? > > >> Thanks. >> >> -- >> ?ark Yao >> >> > > -- ?ark Yao
next prev parent reply other threads:[~2016-08-23 0:40 UTC|newest] Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-20 6:18 [PATCH v2 0/5] drm/rockchip: add rk3399 display controller support Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-04-20 6:18 ` [PATCH v2 1/5] drm/rockchip: sort registers define by chip's number Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-06-02 6:51 ` Tomasz Figa 2016-06-02 7:05 ` Mark yao 2016-08-17 17:20 ` [PATCH v3 " Sean Paul 2016-08-17 17:20 ` Sean Paul 2016-08-17 17:20 ` Sean Paul 2016-08-18 9:08 ` Mark yao 2016-08-18 9:08 ` Mark yao 2016-08-18 9:08 ` Mark yao 2016-08-18 9:11 ` Daniel Vetter 2016-08-18 9:11 ` Daniel Vetter 2016-08-18 9:11 ` Daniel Vetter 2016-08-18 10:02 ` Mark yao 2016-08-18 10:02 ` Mark yao 2016-08-18 10:02 ` Mark yao 2016-08-22 20:30 ` Sean Paul 2016-08-22 20:30 ` Sean Paul 2016-08-22 20:30 ` Sean Paul 2016-08-23 0:40 ` Mark yao [this message] 2016-08-23 0:40 ` Mark yao 2016-08-23 13:13 ` Sean Paul 2016-08-23 13:13 ` Sean Paul 2016-08-23 13:13 ` Sean Paul 2016-08-25 2:25 ` Mark yao 2016-08-25 2:25 ` Mark yao 2016-08-25 2:25 ` Mark yao 2016-08-25 17:15 ` Sean Paul 2016-08-25 17:17 ` Sean Paul 2016-08-25 17:17 ` Sean Paul 2016-08-25 17:17 ` Sean Paul 2016-04-20 6:18 ` [PATCH v2 2/5] dt-bindings: sort Rockchip vop compatible " Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-06-02 6:56 ` Tomasz Figa 2016-08-17 17:11 ` [PATCH v3 " Sean Paul 2016-08-17 17:11 ` Sean Paul 2016-08-17 17:11 ` Sean Paul 2016-08-18 21:15 ` Sean Paul 2016-08-18 21:15 ` Sean Paul 2016-08-18 21:15 ` Sean Paul 2016-08-19 13:51 ` Rob Herring 2016-08-19 13:51 ` Rob Herring 2016-08-19 13:51 ` Rob Herring 2016-04-20 6:18 ` [PATCH v2 3/5] drm/rockchip: vop: introduce VOP_REG_MASK Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-06-02 7:19 ` Tomasz Figa 2016-08-17 17:23 ` [PATCH v3 " Sean Paul 2016-08-17 17:23 ` Sean Paul 2016-08-17 17:23 ` Sean Paul 2016-04-20 6:18 ` [PATCH v2 4/5] drm/rockchip: vop: add rk3399 vop support Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-04-20 6:18 ` Mark Yao 2016-06-02 7:27 ` Tomasz Figa 2016-04-20 6:20 ` [PATCH v2 5/5] dt-bindings: add documentation for Rockchip rk3399 display controllers Mark Yao 2016-04-20 6:20 ` Mark Yao 2016-04-20 6:20 ` Mark Yao 2016-06-02 7:33 ` Tomasz Figa 2016-08-17 17:16 ` [PATCH v3 5/5] dt-bindings: add compatible strings for big/little rockchip vops Sean Paul 2016-08-17 17:16 ` Sean Paul 2016-08-17 17:16 ` Sean Paul [not found] <0001-<1471454202-1631-1-git-send-email-seanpaul@chromium.org> 2016-08-18 21:12 ` Sean Paul 2016-08-18 21:12 ` Sean Paul 2016-08-18 21:12 ` Sean Paul 2016-08-19 13:50 ` Rob Herring 2016-08-19 13:50 ` Rob Herring 2016-08-19 13:50 ` Rob Herring
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=57BB9B87.2040406@rock-chips.com \ --to=mark.yao@rock-chips.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=seanpaul@chromium.org \ --cc=tfiga@chromium.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: linkBe 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.