* Re: Please pull ARCPGU changes
@ 2017-08-02 9:41 ` Daniel Vetter
0 siblings, 0 replies; 13+ messages in thread
From: Daniel Vetter @ 2017-08-02 9:41 UTC (permalink / raw)
To: Alexey Brodkin
Cc: airlied@gmail.com, Jose Abreu, Carlos Palminha,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
daniel.vetter@intel.com, linux-snps-arc@lists.infradead.org
On Mon, Jul 31, 2017 at 11:11:06AM +0000, Alexey Brodkin wrote:
> Hi Dave,
>
> Could you please pull a couple of minor fixes for ARCPGU.
> These changes are based on today's drm-misc/drm-misc-next.
You can't send Dave a pull based on a random snapshot of drm-misc-next. If
you want to maintain your driver on top of drm-misc, then become part of
the group (arcgpu would fit imo). Otherwise you need to base your pulls on
top of Dave's tree. Also, your pull is missing the [PULL] tag in the
subject.
-Daniel
>
> The following changes since commit 9dd2aca46a13cc7177625f0dc3aaf5b7ebc6fe74:
>
> drm/rockchip: vop: rk3328: fix overlay abnormal (2017-07-31 08:44:18 +0800)
>
> are available in the git repository at:
>
> https://github.com/foss-for-synopsys-dwc-arc-processors/linux topic-arcpgu-updates
>
> for you to fetch changes up to a8709950755748e9975d63faa624f2ba4b39f9d6:
>
> drm: arcpgu: Allow some clock deviation in crtc->mode_valid() callback (2017-07-31 14:05:21 +0300)
>
> ----------------------------------------------------------------
> Alexey Brodkin (2):
> drm/arcpgu: Opt in debugfs
> arcpgu: Simplify driver name
>
> Jose Abreu (3):
> drm: arcpgu: Fix mmap() callback
> drm: arcpgu: Fix module unload
> drm: arcpgu: Allow some clock deviation in crtc->mode_valid() callback
>
> drivers/gpu/drm/arc/arcpgu_crtc.c | 7 ++++---
> drivers/gpu/drm/arc/arcpgu_drv.c | 57 ++++++++++++++++++++++++++++++++-------------------------
> 2 files changed, 36 insertions(+), 28 deletions(-)
>
> Regards,
> Alexey
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Please pull ARCPGU changes
@ 2017-08-02 9:41 ` Daniel Vetter
0 siblings, 0 replies; 13+ messages in thread
From: Daniel Vetter @ 2017-08-02 9:41 UTC (permalink / raw)
To: Alexey Brodkin
Cc: Jose Abreu, Carlos Palminha, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, daniel.vetter@intel.com,
linux-snps-arc@lists.infradead.org
On Mon, Jul 31, 2017 at 11:11:06AM +0000, Alexey Brodkin wrote:
> Hi Dave,
>
> Could you please pull a couple of minor fixes for ARCPGU.
> These changes are based on today's drm-misc/drm-misc-next.
You can't send Dave a pull based on a random snapshot of drm-misc-next. If
you want to maintain your driver on top of drm-misc, then become part of
the group (arcgpu would fit imo). Otherwise you need to base your pulls on
top of Dave's tree. Also, your pull is missing the [PULL] tag in the
subject.
-Daniel
>
> The following changes since commit 9dd2aca46a13cc7177625f0dc3aaf5b7ebc6fe74:
>
> drm/rockchip: vop: rk3328: fix overlay abnormal (2017-07-31 08:44:18 +0800)
>
> are available in the git repository at:
>
> https://github.com/foss-for-synopsys-dwc-arc-processors/linux topic-arcpgu-updates
>
> for you to fetch changes up to a8709950755748e9975d63faa624f2ba4b39f9d6:
>
> drm: arcpgu: Allow some clock deviation in crtc->mode_valid() callback (2017-07-31 14:05:21 +0300)
>
> ----------------------------------------------------------------
> Alexey Brodkin (2):
> drm/arcpgu: Opt in debugfs
> arcpgu: Simplify driver name
>
> Jose Abreu (3):
> drm: arcpgu: Fix mmap() callback
> drm: arcpgu: Fix module unload
> drm: arcpgu: Allow some clock deviation in crtc->mode_valid() callback
>
> drivers/gpu/drm/arc/arcpgu_crtc.c | 7 ++++---
> drivers/gpu/drm/arc/arcpgu_drv.c | 57 ++++++++++++++++++++++++++++++++-------------------------
> 2 files changed, 36 insertions(+), 28 deletions(-)
>
> Regards,
> Alexey
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Please pull ARCPGU changes
2017-08-02 9:41 ` Daniel Vetter
@ 2017-08-02 10:16 ` Alexey Brodkin
-1 siblings, 0 replies; 13+ messages in thread
From: Alexey Brodkin @ 2017-08-02 10:16 UTC (permalink / raw)
To: linux-snps-arc
Hi Daniel,
On Wed, 2017-08-02@11:41 +0200, Daniel Vetter wrote:
> On Mon, Jul 31, 2017@11:11:06AM +0000, Alexey Brodkin wrote:
> >
> > Hi Dave,
> >
> > Could you please pull a couple of minor fixes for ARCPGU.
> > These changes are based on today's drm-misc/drm-misc-next.
>
> You can't send Dave a pull based on a random snapshot of drm-misc-next. If
> you want to maintain your driver on top of drm-misc, then become part of
> the group (arcgpu would fit imo). Otherwise you need to base your pulls on
> top of Dave's tree.
I don't have any specific requirement for "drm-misc-next" to b used as a base.
That said Dave trees are OK for me. Still could you please point me to
his "for-curr" and "for-next" (or equivalent) trees?
> Also, your pull is missing the [PULL] tag in the
> subject.
Sorry for that, will fix it in the next request.
-Alexey
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Please pull ARCPGU changes
@ 2017-08-02 10:16 ` Alexey Brodkin
0 siblings, 0 replies; 13+ messages in thread
From: Alexey Brodkin @ 2017-08-02 10:16 UTC (permalink / raw)
To: daniel@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, airlied@gmail.com,
Jose.Abreu@synopsys.com, CARLOS.PALMINHA@synopsys.com,
linux-kernel@vger.kernel.org, daniel.vetter@intel.com,
linux-snps-arc@lists.infradead.org
Hi Daniel,
On Wed, 2017-08-02 at 11:41 +0200, Daniel Vetter wrote:
> On Mon, Jul 31, 2017 at 11:11:06AM +0000, Alexey Brodkin wrote:
> >
> > Hi Dave,
> >
> > Could you please pull a couple of minor fixes for ARCPGU.
> > These changes are based on today's drm-misc/drm-misc-next.
>
> You can't send Dave a pull based on a random snapshot of drm-misc-next. If
> you want to maintain your driver on top of drm-misc, then become part of
> the group (arcgpu would fit imo). Otherwise you need to base your pulls on
> top of Dave's tree.
I don't have any specific requirement for "drm-misc-next" to b used as a base.
That said Dave trees are OK for me. Still could you please point me to
his "for-curr" and "for-next" (or equivalent) trees?
> Also, your pull is missing the [PULL] tag in the
> subject.
Sorry for that, will fix it in the next request.
-Alexey
^ permalink raw reply [flat|nested] 13+ messages in thread
* Please pull ARCPGU changes
2017-08-02 10:16 ` Alexey Brodkin
@ 2017-08-02 18:24 ` Alex Deucher
-1 siblings, 0 replies; 13+ messages in thread
From: Alex Deucher @ 2017-08-02 18:24 UTC (permalink / raw)
To: linux-snps-arc
On Wed, Aug 2, 2017 at 6:16 AM, Alexey Brodkin
<Alexey.Brodkin@synopsys.com> wrote:
> Hi Daniel,
>
> On Wed, 2017-08-02@11:41 +0200, Daniel Vetter wrote:
>> On Mon, Jul 31, 2017@11:11:06AM +0000, Alexey Brodkin wrote:
>> >
>> > Hi Dave,
>> >
>> > Could you please pull a couple of minor fixes for ARCPGU.
>> > These changes are based on today's drm-misc/drm-misc-next.
>>
>> You can't send Dave a pull based on a random snapshot of drm-misc-next. If
>> you want to maintain your driver on top of drm-misc, then become part of
>> the group (arcgpu would fit imo). Otherwise you need to base your pulls on
>> top of Dave's tree.
>
> I don't have any specific requirement for "drm-misc-next" to b used as a base.
> That said Dave trees are OK for me. Still could you please point me to
> his "for-curr" and "for-next" (or equivalent) trees?
next:
https://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next
fixes:
https://cgit.freedesktop.org/~airlied/linux/log/?h=drm-fixes
Alex
>
>> Also, your pull is missing the [PULL] tag in the
>> subject.
>
> Sorry for that, will fix it in the next request.
>
> -Alexey
> _______________________________________________
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Please pull ARCPGU changes
@ 2017-08-02 18:24 ` Alex Deucher
0 siblings, 0 replies; 13+ messages in thread
From: Alex Deucher @ 2017-08-02 18:24 UTC (permalink / raw)
To: Alexey Brodkin
Cc: daniel@ffwll.ch, Jose.Abreu@synopsys.com,
CARLOS.PALMINHA@synopsys.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, daniel.vetter@intel.com,
linux-snps-arc@lists.infradead.org
On Wed, Aug 2, 2017 at 6:16 AM, Alexey Brodkin
<Alexey.Brodkin@synopsys.com> wrote:
> Hi Daniel,
>
> On Wed, 2017-08-02 at 11:41 +0200, Daniel Vetter wrote:
>> On Mon, Jul 31, 2017 at 11:11:06AM +0000, Alexey Brodkin wrote:
>> >
>> > Hi Dave,
>> >
>> > Could you please pull a couple of minor fixes for ARCPGU.
>> > These changes are based on today's drm-misc/drm-misc-next.
>>
>> You can't send Dave a pull based on a random snapshot of drm-misc-next. If
>> you want to maintain your driver on top of drm-misc, then become part of
>> the group (arcgpu would fit imo). Otherwise you need to base your pulls on
>> top of Dave's tree.
>
> I don't have any specific requirement for "drm-misc-next" to b used as a base.
> That said Dave trees are OK for me. Still could you please point me to
> his "for-curr" and "for-next" (or equivalent) trees?
next:
https://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next
fixes:
https://cgit.freedesktop.org/~airlied/linux/log/?h=drm-fixes
Alex
>
>> Also, your pull is missing the [PULL] tag in the
>> subject.
>
> Sorry for that, will fix it in the next request.
>
> -Alexey
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Please pull ARCPGU changes
2017-08-02 18:24 ` Alex Deucher
@ 2017-08-02 21:21 ` Alexey Brodkin
-1 siblings, 0 replies; 13+ messages in thread
From: Alexey Brodkin @ 2017-08-02 21:21 UTC (permalink / raw)
To: linux-snps-arc
Hi Alex,
On Wed, 2017-08-02@14:24 -0400, Alex Deucher wrote:
> On Wed, Aug 2, 2017 at 6:16 AM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
> >
> > Hi Daniel,
> >
> > On Wed, 2017-08-02@11:41 +0200, Daniel Vetter wrote:
> > >
> > > On Mon, Jul 31, 2017@11:11:06AM +0000, Alexey Brodkin wrote:
> > > >
> > > >
> > > > Hi Dave,
> > > >
> > > > Could you please pull a couple of minor fixes for ARCPGU.
> > > > These changes are based on today's drm-misc/drm-misc-next.
> > >
> > > You can't send Dave a pull based on a random snapshot of drm-misc-next. If
> > > you want to maintain your driver on top of drm-misc, then become part of
> > > the group (arcgpu would fit imo). Otherwise you need to base your pulls on
> > > top of Dave's tree.
> >
> > I don't have any specific requirement for "drm-misc-next" to b used as a base.
> > That said Dave trees are OK for me. Still could you please point me to
> > his "for-curr" and "for-next" (or equivalent) trees?
>
> next:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cgit.freedesktop.org_-7Eairlied_linux_log_-3Fh-3Ddrm-2Dnext&d=DwIBaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r
> =lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=pbG-5bjYHB5-5W7BvTn5O7AaB-7boN5rb88XcxgLT5s&s=WrBr72Zx251yCmFMiv7mH7uKt5omhSWk8vlr0GDvG60&e=?
>
> fixes:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cgit.freedesktop.org_-7Eairlied_linux_log_-3Fh-3Ddrm-2Dfixes&d=DwIBaQ&c=DPL6_X_6JkXFx7AXWqB0tg&
> r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=pbG-5bjYHB5-5W7BvTn5O7AaB-7boN5rb88XcxgLT5s&s=iRx0mpfiNcQURDcMGyXfb9arq0OQsCnMddGvXDVk7Zg&e=?
I added this repo as a remote and sent new pull-request based on drm-next.
Thanks a lot for your help.
-Alexey
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Please pull ARCPGU changes
@ 2017-08-02 21:21 ` Alexey Brodkin
0 siblings, 0 replies; 13+ messages in thread
From: Alexey Brodkin @ 2017-08-02 21:21 UTC (permalink / raw)
To: alexdeucher@gmail.com
Cc: daniel@ffwll.ch, Jose.Abreu@synopsys.com,
linux-kernel@vger.kernel.org, CARLOS.PALMINHA@synopsys.com,
daniel.vetter@intel.com, dri-devel@lists.freedesktop.org,
linux-snps-arc@lists.infradead.org
Hi Alex,
On Wed, 2017-08-02 at 14:24 -0400, Alex Deucher wrote:
> On Wed, Aug 2, 2017 at 6:16 AM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
> >
> > Hi Daniel,
> >
> > On Wed, 2017-08-02 at 11:41 +0200, Daniel Vetter wrote:
> > >
> > > On Mon, Jul 31, 2017 at 11:11:06AM +0000, Alexey Brodkin wrote:
> > > >
> > > >
> > > > Hi Dave,
> > > >
> > > > Could you please pull a couple of minor fixes for ARCPGU.
> > > > These changes are based on today's drm-misc/drm-misc-next.
> > >
> > > You can't send Dave a pull based on a random snapshot of drm-misc-next. If
> > > you want to maintain your driver on top of drm-misc, then become part of
> > > the group (arcgpu would fit imo). Otherwise you need to base your pulls on
> > > top of Dave's tree.
> >
> > I don't have any specific requirement for "drm-misc-next" to b used as a base.
> > That said Dave trees are OK for me. Still could you please point me to
> > his "for-curr" and "for-next" (or equivalent) trees?
>
> next:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cgit.freedesktop.org_-7Eairlied_linux_log_-3Fh-3Ddrm-2Dnext&d=DwIBaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r
> =lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=pbG-5bjYHB5-5W7BvTn5O7AaB-7boN5rb88XcxgLT5s&s=WrBr72Zx251yCmFMiv7mH7uKt5omhSWk8vlr0GDvG60&e=
>
> fixes:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cgit.freedesktop.org_-7Eairlied_linux_log_-3Fh-3Ddrm-2Dfixes&d=DwIBaQ&c=DPL6_X_6JkXFx7AXWqB0tg&
> r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=pbG-5bjYHB5-5W7BvTn5O7AaB-7boN5rb88XcxgLT5s&s=iRx0mpfiNcQURDcMGyXfb9arq0OQsCnMddGvXDVk7Zg&e=
I added this repo as a remote and sent new pull-request based on drm-next.
Thanks a lot for your help.
-Alexey
^ permalink raw reply [flat|nested] 13+ messages in thread