lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 20 Aug 2020 08:40:30 +0200
From:   Mauro Carvalho Chehab <>
To:     Sam Ravnborg <>
Cc:     John Stultz <>,
        Greg Kroah-Hartman <>,,,
        Manivannan Sadhasivam <>,
        Daniel Vetter <>,
        dri-devel <>,
        Bogdan Togorean <>,
        Liwei Cai <>,
        linux-arm-kernel <>,
        Daniel Borkmann <>,
        Rob Herring <>,
        "David S. Miller" <>,
        Xinliang Liu <>,
        Neil Armstrong <>,
        Wanchun Zheng <>,
        driverdevel <>,
        BPF Mailing List <>,
        Xiubin Zhang <>,
        linux-media <>,
        Tomi Valkeinen <>,
        Jesper Dangaard Brouer <>,
        Laurent Pinchart <>,
        Xinwei Kong <>,
        Alexei Starovoitov <>,
        <>, Rob Clark <>,
        Laurentiu Palcu <>,
        Andrzej Hajda <>,
        John Fastabend <>,
        Liuyao An <>,
        "moderated list:DMA BUFFER SHARING FRAMEWORK" 
        <>, Wei Xu <>,
        Rongrong Zou <>,
        Philipp Zabel <>,
        Network Development <>,
        Sumit Semwal <>,
        lkml <>,
        Jakub Kicinski <>,
        David Airlie <>,
        Chen Feng <>
Subject: Re: [PATCH 00/49] DRM driver for Hikey 970

Em Wed, 19 Aug 2020 23:25:51 +0200
Sam Ravnborg <> escreveu:

> Hi John.
> > > So, IMO, the best is to keep it on staging for a while, until those
> > > remaining bugs gets solved.  
> > 
> > I'm not sure I see all of these as compelling for pushing it in via
> > staging. And I suspect in the process of submitting the patches for
> > review folks may find the cause of some of the problems you list here.  
> There is a tendency to forget drivers in staging, and with the almost
> constant refactoring that happens in the drm drivers we would end up
> fixing this driver when a bot trigger an error.
> So IMO we need very good reasons to go in via staging.

My plan is to have this driver upstream for 5.10, and getting it
out of staging by Kernel 5.11. So, I doubt that the DRM kAPIs would
change a lot during those 2 Kernel cycles.

In any case, I'm also fine to have a final patch at the end of this
series moving it out of staging. The only thing that, IMHO, prevents
it to be out of staging is the LDI underflow. Right now, if no input
events reach the driver, DPMS will put the monitor to suspend, and
it never returns back from life. I bet that, once we discover the
root cause, the fix would be just a couple of lines, but identifying
where the problem is can take a while.


Powered by blists - more mailing lists