linux-kernel - Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 16 Feb 2017 13:43:06 +0100
From:   Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>
To:     ML dri-devel <dri-devel@...ts.freedesktop.org>
Cc:     maxime.ripard@...e-electrons.com, Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>, wens@...e.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        thomas.petazzoni@...e-electrons.com, devicetree@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

Hello,

I was wondering about the following. Wasn't there some strict
requirement about code going upstream, which also included that there
was a full open-source driver stack for it?

I don't see how this is the case for Mali, neither in the kernel, nor in
userspace. I'm aware that the Mali kernel driver is open-source. But it
is not upstream, maintained out of tree, and won't land upstream in its
current form (no resemblence to a DRM driver at all). And let's not talk
about the userspace part.

So, why should this be here?

With best wishes,
Tobias

P.S.: I'm signed up to dri-devel in digest mode, so sorry if this mail
doesn't properly show up in the corresponding ml thread.