On Fri, Aug 02, 2019 at 03:43:48PM +0200, Maarten Lankhorst wrote:
> Hey,
>
> Bit late, but fixes for v5.3-rc3. :)
Yes, please try to prep and send out -fixes pull on Thu latest. Otherwise
there's no time to fix things up and it eats into w/e ...
>
> drm-misc-fixes-2019-08-02:
> drm-misc-fixes
Hey,
Bit late, but fixes for v5.3-rc3. :)
drm-misc-fixes-2019-08-02:
drm-misc-fixes for v5.3-rc3:
- Fix some build errors in drm/bridge.
- Do not build i810 on CONFIG_PREEMPTION.
- Fix cache sync on arm in vgem.
- Allow mapping fb in drm_client only when required, and use it to fix bochs
fbdev.
Hi,
> I apologize for not having fixes for a couple of weeks, and then showing
> up late with a bunch of them. I saw Dave make the fixes pull to Linus
> for -rc3 already, but I must humbly ask you to accommodate an extra
> fixes pull.
If there is an extra -rc3 fixes pull anyway it would be nice
On Tue, 05 Mar 2019, Lucas De Marchi wrote:
> I myself missed that we had this page for a long time since it's not
> positioned as something to be the first thing to do.
This seems to have fallen through the cracks, pushed patch 1, but there
seem to be open review comments with patch 2.
BR,
Jani
On Fri, 02 Aug 2019, Jani Nikula wrote:
> On Fri, 05 Jul 2019, Arkadiusz Hiler wrote:
>> If patch happens to move lines around it's easy to end in a situation
>> where we end up with errors just moving around:
>>
>> -error1:123
>> error2:124
>> +error1:125
>>
>> With remapping, sorting and then
On Fri, 05 Jul 2019, Arkadiusz Hiler wrote:
> If patch happens to move lines around it's easy to end in a situation
> where we end up with errors just moving around:
>
> -error1:123
> error2:124
> +error1:125
>
> With remapping, sorting and then diffing without context we end up with:
> -error1:1
On Tue, 23 Jul 2019, Maxime Ripard wrote:
> Let's change my email address to the kernel.org one.
Thanks, pushed.
BR,
Jani.
>
> Signed-off-by: Maxime Ripard
> ---
> dim | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dim b/dim
> index bada79cd8523..ccb63d9ee579 100755
Hi Dave and Daniel -
First off, we failed to explicitly agree who's going to cover me
handling the v5.3 fixes during my time off. So it ended up not
happening, and I was faced with quite the backlog. On top of that,
testing uncovered lockdep issues that needed to be addressed before
sending the p