linux-kernel - Re: [RFC AFBC 03/12] drm/afbc: Add AFBC modifier usage documentation

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-prev] [day] [month] [year] [list]

Date:   Mon, 14 Jan 2019 16:24:33 +0200
From:   Jani Nikula <jani.nikula@...ux.intel.com>
To:     Brian Starkey <Brian.Starkey@....com>
Cc:     Liviu Dudau <Liviu.Dudau@....com>,
        Ezequiel Garcia <ezequiel@...labora.com>, nd <nd@....com>,
        "linux-doc\@vger.kernel.org" <linux-doc@...r.kernel.org>,
        "arnd\@arndb.de" <arnd@...db.de>,
        "corbet\@lwn.net" <corbet@....net>,
        "airlied\@linux.ie" <airlied@...ux.ie>,
        "gregkh\@linuxfoundation.org" <gregkh@...uxfoundation.org>,
        "nicolas.ferre\@microchip.com" <nicolas.ferre@...rochip.com>,
        "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
        "dri-devel\@lists.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        "davem\@davemloft.net" <davem@...emloft.net>,
        "maxime.ripard\@bootlin.com" <maxime.ripard@...tlin.com>,
        "malidp\@foss.arm.com" <malidp@...s.arm.com>,
        "mchehab+samsung\@kernel.org" <mchehab+samsung@...nel.org>,
        "akpm\@linux-foundation.org" <akpm@...ux-foundation.org>,
        Ayan Halder <Ayan.Halder@....com>,
        "sean\@poorly.run" <sean@...rly.run>
Subject: Re: [RFC AFBC 03/12] drm/afbc: Add AFBC modifier usage documentation

On Mon, 14 Jan 2019, Brian Starkey <Brian.Starkey@....com> wrote:
> AFBC is a relatively well-established name, whereas arm-fbc is not a
> term anyone will be familiar with.

First time I ever heard of AFBC. ;)

> We could name the file "arm-afbc.rst", though I am slightly against
> namespacing it that way for the reason mentioned above - it
> does/will/should apply to more than just the gpu/drm/arm tree.

Fair enough. It's not like the name is part of the ABI, so I guess let's
go with this, and we can rename later if we come up with a better name.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center