lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170131143853.GU20076@art_vandelay>
Date:   Tue, 31 Jan 2017 09:38:53 -0500
From:   Sean Paul <seanpaul@...omium.org>
To:     Thierry Reding <thierry.reding@...il.com>
Cc:     Inki Dae <inki.dae@...sung.com>, linux-samsung-soc@...r.kernel.org,
        cw00.choi@...sung.com, andi.shyti@...sung.com,
        devicetree@...r.kernel.org, Donghwa Lee <dh09.lee@...sung.com>,
        linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
        jh80.chung@...sung.com, kgene@...nel.org,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Hyungwon Hwang <human.hwang@...sung.com>,
        Hoegeun Kwon <hoegeun.kwon@...sung.com>
Subject: Re: [PATCH v8 2/3] drm/panel: Add support for S6E3HA2 panel driver
 on TM2 board

On Tue, Jan 31, 2017 at 09:54:49AM +0100, Thierry Reding wrote:
> On Tue, Jan 31, 2017 at 09:01:07AM +0900, Inki Dae wrote:
> > 
> > 
> > 2017년 01월 24일 10:50에 Hoegeun Kwon 이(가) 쓴 글:
> > > Dear Thierry,
> > > 
> > > Could you please review this patch?
> > 
> > Thierry, I think this patch has been reviewed enough but no comment
> > from you. Seems you are busy. I will pick up this.
> 
> Sorry, but that's not how it works. This patch has gone through 8
> revisions within 4 weeks, and I tend to ignore patches like that until
> the dust settles.
> 

Seems like the dust was pretty settled. It was posted on 1/11, pinged on 1/24,
and picked up on 1/31. I don't think it's unreasonable to take it through
another tree after that.

I wonder if drm_panel would benefit from the -misc group maintainership model
as drm_bridge does. By spreading out the workload, the high-maintenance
patches would hopefully find someone to shepherd them through.

> Other than that, this continues the same madness that I've repeatedly
> complained about in the past. The whole mechanism of running through a
> series of writes and not caring about errors until the very end is
> something we've discussed at length in the past. It also in large parts
> duplicates a bunch of functions from other Samsung panel drivers that I
> already said should eventually be moved to something saner.
> 

FWIW, this type of error handling isn't my preference either. If we must defer,
I'd rather not keep it in ctx, but rather pass around an argument so it's more
obvious we need to deal with it in the return. That said, this seems like
a case of letting the perfect be the enemy of the good, surely something is
better than nothing?

Sean



> This is now the third driver and nobody's giving a damn about improving
> things.
> 
> Until somebody does, I'm going to have to NAK this.
> 
> Thierry
> 

<snip>

-- 
Sean Paul, Software Engineer, Google / Chromium OS

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ