linux-kernel - Re: [PATCH v2 21/29] drm/rockchip: switch to drm_*_get(), drm_*

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: <CAOw6vb+Y2QNKkvR_Mp5_UCtGdTN+in52BZoB3PrLxv2BmgpDjw@mail.gmail.com>
Date:   Thu, 10 Aug 2017 15:55:46 -0400
From:   Sean Paul <seanpaul@...omium.org>
To:     Cihangir Akturk <cakturk@...il.com>
Cc:     Heiko Stuebner <heiko@...ech.de>,
        "open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
        David Airlie <airlied@...ux.ie>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        Daniel Vetter <daniel@...ll.ch>,
        Linux ARM Kernel <linux-arm-kernel@...ts.infradead.org>,
        Mark Yao <mark.yao@...k-chips.com>
Subject: Re: [PATCH v2 21/29] drm/rockchip: switch to drm_*_get(), drm_*_put() helpers

On Thu, Aug 10, 2017 at 3:52 PM, Cihangir Akturk <cakturk@...il.com> wrote:
> On Thu, Aug 10, 2017 at 02:16:08PM -0400, Sean Paul wrote:
>> On Thu, Aug 10, 2017 at 03:10:04PM +0300, Cihangir Akturk wrote:
>> > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference()
>> > and drm_*_unreference() helpers.
>> >
>> > drm_*_reference() and drm_*_unreference() functions are just
>> > compatibility alias for drm_*_get() and drm_*_put() and should not be
>> > used by new code. So convert all users of compatibility functions to
>> > use the new APIs.
>> >
>> > Generated by: scripts/coccinelle/api/drm-get-put.cocci
>> >
>> > Signed-off-by: Cihangir Akturk <cakturk@...il.com>
>>
>> Hi Cihangir,
>> Thank you for the patch. Unfortunately it does not apply to drm-misc-next. Could
>> you please resend with conflicts resolved?
>
> OK, I'll send a v3 based on drm-next.

*drm-misc-next

> And should I drop patches from
> v1 already pulled in drm-next?
>

yes please

Sean


> Thanks, Cihangir
>
>>
>> Thanks,
>>
>> Sean
>>