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] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 1 Jun 2018 09:44:15 -0400
From:   Alex Deucher <alexdeucher@...il.com>
To:     Michel Dänzer <michel@...nzer.net>
Cc:     Maling list - DRI developers <dri-devel@...ts.freedesktop.org>,
        Jonathan Corbet <corbet@....net>,
        LKML <linux-kernel@...r.kernel.org>,
        amd-gfx list <amd-gfx@...ts.freedesktop.org>,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH 3/3] drm/amdgpu: Add documentation for PRIME related code

On Fri, Jun 1, 2018 at 9:40 AM, Michel Dänzer <michel@...nzer.net> wrote:
> On 2018-06-01 02:58 PM, Alex Deucher wrote:
>> On Thu, May 31, 2018 at 12:17 PM, Michel Dänzer <michel@...nzer.net> wrote:
>>> From: Michel Dänzer <michel.daenzer@....com>
>>>
>>> Signed-off-by: Michel Dänzer <michel.daenzer@....com>
>>
>> Series is:
>> Reviewed-by: Alex Deucher <alexander.deucher@....com>
>
> Thanks. Is it okay to merge all of these via the amdgpu tree, or should
> I wait for an ack from Jon and/or core DRM maintainers for that?

GPU documentation usually goes through the drm trees.  You might want
to push patch 1 (drm_mm.rst fix) via drm_misc, but the rest are can go
in via the amdgpu tree since they are amdgpu specific.

Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ