[PULL] mxsfb fixes

[PULL] mxsfb fixes

[Marek Vasut]

Hi,

I collected the MXSFB fixes, based on top of airlied/drm-fixes:

The following changes since commit 697d3a21615672b2bf7724a65755799260325dda:

  Merge tag 'drm-intel-fixes-2017-02-09' of
git://anongit.freedesktop.org/git/drm-intel into drm-fixes (2017-02-10
10:14:24 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
d7a280f2cc3860b0783fac9e8c5c223b8bdaea5c

for you to fetch changes up to d7a280f2cc3860b0783fac9e8c5c223b8bdaea5c:

  drm: mxsfb: Implement drm_panel handling (2017-02-14 05:35:56 +0100)

----------------------------------------------------------------
Fabio Estevam (2):
      drm: mxsfb_crtc: Fix the framebuffer misplacement
      drm: mxsfb: Implement drm_panel handling

Marek Vasut (1):
      drm: mxsfb: Fix crash when provided invalid DT bindings

Stefan Agner (2):
      drm: mxsfb: use bus_format to determine LCD bus width
      drm: mxsfb: fix pixel clock polarity

 drivers/gpu/drm/mxsfb/mxsfb_crtc.c | 49
+++++++++++++++++++++++++++++++++++++++++++------
 drivers/gpu/drm/mxsfb/mxsfb_drv.c  |  4 ++++
 drivers/gpu/drm/mxsfb/mxsfb_out.c  |  4 ++++
 drivers/gpu/drm/mxsfb/mxsfb_regs.h |  1 +
 4 files changed, 52 insertions(+), 6 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Dave Airlie]

On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
> Hi,
>
> I collected the MXSFB fixes, based on top of airlied/drm-fixes:

At this stage I'd rather not give these to Linus, can you rebase them onto
drm-next, and resend, feel free to add stable cc's.

Fixes like this should really be getting to me sooner than rc8.

Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Marek Vasut]

On 02/17/2017 03:41 AM, Dave Airlie wrote:
> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>> Hi,
>>
>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
> 
> At this stage I'd rather not give these to Linus, can you rebase them onto
> drm-next, and resend, feel free to add stable cc's.
> 
> Fixes like this should really be getting to me sooner than rc8.

I know, sorry about that. I was totally overloaded in the past weeks.
What about getting them to rc1, any chance for that ?

-- 
Best regards,
Marek Vasut
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Dave Airlie]

On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
> On 02/17/2017 03:41 AM, Dave Airlie wrote:
>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>>> Hi,
>>>
>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
>>
>> At this stage I'd rather not give these to Linus, can you rebase them onto
>> drm-next, and resend, feel free to add stable cc's.
>>
>> Fixes like this should really be getting to me sooner than rc8.
>
> I know, sorry about that. I was totally overloaded in the past weeks.
> What about getting them to rc1, any chance for that ?

Yes if you can rebase them onto drm-next.

Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Marek Vasut]

On 02/17/2017 09:34 PM, Dave Airlie wrote:
> On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
>> On 02/17/2017 03:41 AM, Dave Airlie wrote:
>>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>>>> Hi,
>>>>
>>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
>>>
>>> At this stage I'd rather not give these to Linus, can you rebase them onto
>>> drm-next, and resend, feel free to add stable cc's.
>>>
>>> Fixes like this should really be getting to me sooner than rc8.
>>
>> I know, sorry about that. I was totally overloaded in the past weeks.
>> What about getting them to rc1, any chance for that ?
> 
> Yes if you can rebase them onto drm-next.

Ha, got it. Try the following:

The following changes since commit 9ca70356a9260403c1bda40d942935e55d00c11c:

  Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
c72a2ec8208b40683fbd2970684ffbf3a8c7d17e

for you to fetch changes up to c72a2ec8208b40683fbd2970684ffbf3a8c7d17e:

  drm: mxsfb: Implement drm_panel handling (2017-02-18 23:22:42 +0100)

----------------------------------------------------------------
Fabio Estevam (2):
      drm: mxsfb_crtc: Fix the framebuffer misplacement
      drm: mxsfb: Implement drm_panel handling

Marek Vasut (1):
      drm: mxsfb: Fix crash when provided invalid DT bindings

Stefan Agner (2):
      drm: mxsfb: use bus_format to determine LCD bus width
      drm: mxsfb: fix pixel clock polarity

 drivers/gpu/drm/mxsfb/mxsfb_crtc.c | 49
+++++++++++++++++++++++++++++++++++++++++++------
 drivers/gpu/drm/mxsfb/mxsfb_drv.c  |  4 ++++
 drivers/gpu/drm/mxsfb/mxsfb_out.c  |  4 ++++
 drivers/gpu/drm/mxsfb/mxsfb_regs.h |  1 +
 4 files changed, 52 insertions(+), 6 deletions(-)

-- 
Best regards,
Marek Vasut
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Dave Airlie]

On 19 February 2017 at 08:25, Marek Vasut <marex@denx.de> wrote:
> On 02/17/2017 09:34 PM, Dave Airlie wrote:
>> On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
>>> On 02/17/2017 03:41 AM, Dave Airlie wrote:
>>>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>>>>> Hi,
>>>>>
>>>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
>>>>
>>>> At this stage I'd rather not give these to Linus, can you rebase them onto
>>>> drm-next, and resend, feel free to add stable cc's.
>>>>
>>>> Fixes like this should really be getting to me sooner than rc8.
>>>
>>> I know, sorry about that. I was totally overloaded in the past weeks.
>>> What about getting them to rc1, any chance for that ?
>>
>> Yes if you can rebase them onto drm-next.
>
> Ha, got it. Try the following:
>
> The following changes since commit 9ca70356a9260403c1bda40d942935e55d00c11c:
>
>   Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04 +1000)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
> c72a2ec8208b40683fbd2970684ffbf3a8c7d17e

Nearly, put please use a tag :-)

Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Marek Vasut]

On 02/20/2017 03:56 AM, Dave Airlie wrote:
> On 19 February 2017 at 08:25, Marek Vasut <marex@denx.de> wrote:
>> On 02/17/2017 09:34 PM, Dave Airlie wrote:
>>> On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
>>>> On 02/17/2017 03:41 AM, Dave Airlie wrote:
>>>>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
>>>>>
>>>>> At this stage I'd rather not give these to Linus, can you rebase them onto
>>>>> drm-next, and resend, feel free to add stable cc's.
>>>>>
>>>>> Fixes like this should really be getting to me sooner than rc8.
>>>>
>>>> I know, sorry about that. I was totally overloaded in the past weeks.
>>>> What about getting them to rc1, any chance for that ?
>>>
>>> Yes if you can rebase them onto drm-next.
>>
>> Ha, got it. Try the following:
>>
>> The following changes since commit 9ca70356a9260403c1bda40d942935e55d00c11c:
>>
>>   Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04 +1000)
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
>> c72a2ec8208b40683fbd2970684ffbf3a8c7d17e
> 
> Nearly, put please use a tag :-)

I'm sure you can pull this batch without a tag ;-)
What do you have in mind for the next PR ?

-- 
Best regards,
Marek Vasut
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Dave Airlie]

[-- Attachment #1.1: Type: text/plain, Size: 1538 bytes --]

On 20 Feb. 2017 18:29, "Marek Vasut" <marex@denx.de> wrote:

On 02/20/2017 03:56 AM, Dave Airlie wrote:
> On 19 February 2017 at 08:25, Marek Vasut <marex@denx.de> wrote:
>> On 02/17/2017 09:34 PM, Dave Airlie wrote:
>>> On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
>>>> On 02/17/2017 03:41 AM, Dave Airlie wrote:
>>>>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
>>>>>
>>>>> At this stage I'd rather not give these to Linus, can you rebase them
onto
>>>>> drm-next, and resend, feel free to add stable cc's.
>>>>>
>>>>> Fixes like this should really be getting to me sooner than rc8.
>>>>
>>>> I know, sorry about that. I was totally overloaded in the past weeks.
>>>> What about getting them to rc1, any chance for that ?
>>>
>>> Yes if you can rebase them onto drm-next.
>>
>> Ha, got it. Try the following:
>>
>> The following changes since commit 9ca70356a9260403c1bda40d942935
e55d00c11c:
>>
>>   Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04
+1000)
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
>> c72a2ec8208b40683fbd2970684ffbf3a8c7d17e
>
> Nearly, put please use a tag :-)

I'm sure you can pull this batch without a tag ;-)


No, I really need tags preferably signed.

Otherwise the merge is all ugly.


What do you have in mind for the next PR


Not sure I follow.

Dave


--
Best regards,
Marek Vasut

[-- Attachment #1.2: Type: text/html, Size: 3312 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Marek Vasut]

On 02/20/2017 10:05 AM, Dave Airlie wrote:
> On 20 Feb. 2017 18:29, "Marek Vasut" <marex@denx.de> wrote:
> 
> On 02/20/2017 03:56 AM, Dave Airlie wrote:
>> On 19 February 2017 at 08:25, Marek Vasut <marex@denx.de> wrote:
>>> On 02/17/2017 09:34 PM, Dave Airlie wrote:
>>>> On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
>>>>> On 02/17/2017 03:41 AM, Dave Airlie wrote:
>>>>>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
>>>>>>
>>>>>> At this stage I'd rather not give these to Linus, can you rebase them
> onto
>>>>>> drm-next, and resend, feel free to add stable cc's.
>>>>>>
>>>>>> Fixes like this should really be getting to me sooner than rc8.
>>>>>
>>>>> I know, sorry about that. I was totally overloaded in the past weeks.
>>>>> What about getting them to rc1, any chance for that ?
>>>>
>>>> Yes if you can rebase them onto drm-next.
>>>
>>> Ha, got it. Try the following:
>>>
>>> The following changes since commit 9ca70356a9260403c1bda40d942935
> e55d00c11c:
>>>
>>>   Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04
> +1000)
>>>
>>> are available in the git repository at:
>>>
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
>>> c72a2ec8208b40683fbd2970684ffbf3a8c7d17e
>>
>> Nearly, put please use a tag :-)
> 
> I'm sure you can pull this batch without a tag ;-)
> 
> 
> No, I really need tags preferably signed.
> 
> Otherwise the merge is all ugly.
> 
> 
> What do you have in mind for the next PR
> 
> 
> Not sure I follow.

What do you need to get these five fixes applied, ideally without much
further annoyance to either of us. Ideally point me to some docs.

-- 
Best regards,
Marek Vasut
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Jani Nikula]

On Mon, 20 Feb 2017, Marek Vasut <marex@denx.de> wrote:
> On 02/20/2017 10:05 AM, Dave Airlie wrote:
>> On 20 Feb. 2017 18:29, "Marek Vasut" <marex@denx.de> wrote:
>> 
>> On 02/20/2017 03:56 AM, Dave Airlie wrote:
>>> On 19 February 2017 at 08:25, Marek Vasut <marex@denx.de> wrote:
>>>> On 02/17/2017 09:34 PM, Dave Airlie wrote:
>>>>> On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
>>>>>> On 02/17/2017 03:41 AM, Dave Airlie wrote:
>>>>>>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
>>>>>>>
>>>>>>> At this stage I'd rather not give these to Linus, can you rebase them
>> onto
>>>>>>> drm-next, and resend, feel free to add stable cc's.
>>>>>>>
>>>>>>> Fixes like this should really be getting to me sooner than rc8.
>>>>>>
>>>>>> I know, sorry about that. I was totally overloaded in the past weeks.
>>>>>> What about getting them to rc1, any chance for that ?
>>>>>
>>>>> Yes if you can rebase them onto drm-next.
>>>>
>>>> Ha, got it. Try the following:
>>>>
>>>> The following changes since commit 9ca70356a9260403c1bda40d942935
>> e55d00c11c:
>>>>
>>>>   Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04
>> +1000)
>>>>
>>>> are available in the git repository at:
>>>>
>>>>   git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
>>>> c72a2ec8208b40683fbd2970684ffbf3a8c7d17e
>>>
>>> Nearly, put please use a tag :-)
>> 
>> I'm sure you can pull this batch without a tag ;-)
>> 
>> 
>> No, I really need tags preferably signed.
>> 
>> Otherwise the merge is all ugly.
>> 
>> 
>> What do you have in mind for the next PR
>> 
>> 
>> Not sure I follow.
>
> What do you need to get these five fixes applied, ideally without much
> further annoyance to either of us. Ideally point me to some docs.

Tag the head of the branch you want pulled. Push the tag to the repo you
want Dave to pull from. Generate the pull request using the tag instead
of branch.

Something along the lines of:

$ git tag $tag $remote/$branch
$ git push $remote $tag
$ git request-pull $upstream $url $tag

Replace $vars with what you have. Use git tag -s option to do a signed
tag.

HTH,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Marek Vasut]

On 02/21/2017 09:38 AM, Jani Nikula wrote:
> On Mon, 20 Feb 2017, Marek Vasut <marex@denx.de> wrote:
>> On 02/20/2017 10:05 AM, Dave Airlie wrote:
>>> On 20 Feb. 2017 18:29, "Marek Vasut" <marex@denx.de> wrote:
>>>
>>> On 02/20/2017 03:56 AM, Dave Airlie wrote:
>>>> On 19 February 2017 at 08:25, Marek Vasut <marex@denx.de> wrote:
>>>>> On 02/17/2017 09:34 PM, Dave Airlie wrote:
>>>>>> On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
>>>>>>> On 02/17/2017 03:41 AM, Dave Airlie wrote:
>>>>>>>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
>>>>>>>>
>>>>>>>> At this stage I'd rather not give these to Linus, can you rebase them
>>> onto
>>>>>>>> drm-next, and resend, feel free to add stable cc's.
>>>>>>>>
>>>>>>>> Fixes like this should really be getting to me sooner than rc8.
>>>>>>>
>>>>>>> I know, sorry about that. I was totally overloaded in the past weeks.
>>>>>>> What about getting them to rc1, any chance for that ?
>>>>>>
>>>>>> Yes if you can rebase them onto drm-next.
>>>>>
>>>>> Ha, got it. Try the following:
>>>>>
>>>>> The following changes since commit 9ca70356a9260403c1bda40d942935
>>> e55d00c11c:
>>>>>
>>>>>   Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04
>>> +1000)
>>>>>
>>>>> are available in the git repository at:
>>>>>
>>>>>   git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
>>>>> c72a2ec8208b40683fbd2970684ffbf3a8c7d17e
>>>>
>>>> Nearly, put please use a tag :-)
>>>
>>> I'm sure you can pull this batch without a tag ;-)
>>>
>>>
>>> No, I really need tags preferably signed.
>>>
>>> Otherwise the merge is all ugly.
>>>
>>>
>>> What do you have in mind for the next PR
>>>
>>>
>>> Not sure I follow.
>>
>> What do you need to get these five fixes applied, ideally without much
>> further annoyance to either of us. Ideally point me to some docs.
> 
> Tag the head of the branch you want pulled. Push the tag to the repo you
> want Dave to pull from. Generate the pull request using the tag instead
> of branch.
> 
> Something along the lines of:
> 
> $ git tag $tag $remote/$branch
> $ git push $remote $tag
> $ git request-pull $upstream $url $tag
> 
> Replace $vars with what you have. Use git tag -s option to do a signed
> tag.
> 
> HTH,
> Jani.

Thanks. I know how to do a tag and push it, except it'd be great to have
this process documented somewhere so I don't need to submit such trivial
PR thrice with minor modifications ...

-- 
Best regards,
Marek Vasut
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Marek Vasut]

Here's one with a tag, updated on drm-next again :

The following changes since commit d458079eb403fe4db625af349329e312c976d743:

  drm/tinydrm: fix mipi-dbi warning. (2017-02-24 13:23:36 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
tags/mxsfb-fixes-20170226

for you to fetch changes up to d83574b9f0494d8bc4f00704483c6f1d3cd3ce30:

  drm: mxsfb: Implement drm_panel handling (2017-02-26 13:22:05 +0100)

----------------------------------------------------------------
Fabio Estevam (2):
      drm: mxsfb_crtc: Fix the framebuffer misplacement
      drm: mxsfb: Implement drm_panel handling

Marek Vasut (1):
      drm: mxsfb: Fix crash when provided invalid DT bindings

Stefan Agner (2):
      drm: mxsfb: use bus_format to determine LCD bus width
      drm: mxsfb: fix pixel clock polarity

 drivers/gpu/drm/mxsfb/mxsfb_crtc.c | 49
+++++++++++++++++++++++++++++++++++++++++++------
 drivers/gpu/drm/mxsfb/mxsfb_drv.c  |  4 ++++
 drivers/gpu/drm/mxsfb/mxsfb_out.c  |  4 ++++
 drivers/gpu/drm/mxsfb/mxsfb_regs.h |  1 +
 4 files changed, 52 insertions(+), 6 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] mxsfb fixes

[Daniel Vetter]

On Tue, Feb 21, 2017 at 10:38:20AM +0200, Jani Nikula wrote:
> On Mon, 20 Feb 2017, Marek Vasut <marex@denx.de> wrote:
> > On 02/20/2017 10:05 AM, Dave Airlie wrote:
> >> On 20 Feb. 2017 18:29, "Marek Vasut" <marex@denx.de> wrote:
> >> 
> >> On 02/20/2017 03:56 AM, Dave Airlie wrote:
> >>> On 19 February 2017 at 08:25, Marek Vasut <marex@denx.de> wrote:
> >>>> On 02/17/2017 09:34 PM, Dave Airlie wrote:
> >>>>> On 17 February 2017 at 18:00, Marek Vasut <marex@denx.de> wrote:
> >>>>>> On 02/17/2017 03:41 AM, Dave Airlie wrote:
> >>>>>>> On 16 February 2017 at 08:16, Marek Vasut <marex@denx.de> wrote:
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> I collected the MXSFB fixes, based on top of airlied/drm-fixes:
> >>>>>>>
> >>>>>>> At this stage I'd rather not give these to Linus, can you rebase them
> >> onto
> >>>>>>> drm-next, and resend, feel free to add stable cc's.
> >>>>>>>
> >>>>>>> Fixes like this should really be getting to me sooner than rc8.
> >>>>>>
> >>>>>> I know, sorry about that. I was totally overloaded in the past weeks.
> >>>>>> What about getting them to rc1, any chance for that ?
> >>>>>
> >>>>> Yes if you can rebase them onto drm-next.
> >>>>
> >>>> Ha, got it. Try the following:
> >>>>
> >>>> The following changes since commit 9ca70356a9260403c1bda40d942935
> >> e55d00c11c:
> >>>>
> >>>>   Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04
> >> +1000)
> >>>>
> >>>> are available in the git repository at:
> >>>>
> >>>>   git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
> >>>> c72a2ec8208b40683fbd2970684ffbf3a8c7d17e
> >>>
> >>> Nearly, put please use a tag :-)
> >> 
> >> I'm sure you can pull this batch without a tag ;-)
> >> 
> >> 
> >> No, I really need tags preferably signed.
> >> 
> >> Otherwise the merge is all ugly.
> >> 
> >> 
> >> What do you have in mind for the next PR
> >> 
> >> 
> >> Not sure I follow.
> >
> > What do you need to get these five fixes applied, ideally without much
> > further annoyance to either of us. Ideally point me to some docs.
> 
> Tag the head of the branch you want pulled. Push the tag to the repo you
> want Dave to pull from. Generate the pull request using the tag instead
> of branch.
> 
> Something along the lines of:
> 
> $ git tag $tag $remote/$branch
> $ git push $remote $tag
> $ git request-pull $upstream $url $tag
> 
> Replace $vars with what you have. Use git tag -s option to do a signed
> tag.

Or just come over to the evil side, aka drm-misc, where we have all this
stuff scripted.
-Daniel
-- 
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

Re: [PULL] mxsfb fixes

[Stefan Agner]

Marek, Dave,

On 2017-02-26 04:43, Marek Vasut wrote:
> Here's one with a tag, updated on drm-next again :
> 
> The following changes since commit d458079eb403fe4db625af349329e312c976d743:
> 
>   drm/tinydrm: fix mipi-dbi warning. (2017-02-24 13:23:36 +1000)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/marex/linux-2.6.git
> tags/mxsfb-fixes-20170226


With 4.11-rc1 i.MX 7 fails for me with:
OF: graph: no port node found in /soc/aips-bus@30400000/lcdif@30730000
Unable to handle kernel NULL pointer dereference at virtual address
00000004

Afaik, this should be fixed with ("drm: mxsfb: Fix crash when provided
invalid DT bindings"), but the pull did not make it...

Can we get this into 4.11?

--
Stefan


> 
> for you to fetch changes up to d83574b9f0494d8bc4f00704483c6f1d3cd3ce30:
> 
>   drm: mxsfb: Implement drm_panel handling (2017-02-26 13:22:05 +0100)
> 
> ----------------------------------------------------------------
> Fabio Estevam (2):
>       drm: mxsfb_crtc: Fix the framebuffer misplacement
>       drm: mxsfb: Implement drm_panel handling
> 
> Marek Vasut (1):
>       drm: mxsfb: Fix crash when provided invalid DT bindings
> 
> Stefan Agner (2):
>       drm: mxsfb: use bus_format to determine LCD bus width
>       drm: mxsfb: fix pixel clock polarity
> 
>  drivers/gpu/drm/mxsfb/mxsfb_crtc.c | 49
> +++++++++++++++++++++++++++++++++++++++++++------
>  drivers/gpu/drm/mxsfb/mxsfb_drv.c  |  4 ++++
>  drivers/gpu/drm/mxsfb/mxsfb_out.c  |  4 ++++
>  drivers/gpu/drm/mxsfb/mxsfb_regs.h |  1 +
>  4 files changed, 52 insertions(+), 6 deletions(-)
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel