From: Cihangir Akturk <cakturk@gmail.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
daniel@ffwll.ch, linux-arm-kernel@lists.infradead.org,
Mark Yao <mark.yao@rock-chips.com>
Subject: Re: [PATCH v2 21/29] drm/rockchip: switch to drm_*_get(), drm_*_put() helpers
Date: Thu, 10 Aug 2017 22:52:46 +0300 [thread overview]
Message-ID: <20170810195246.GA951@mbp> (raw)
In-Reply-To: <20170810181608.xtrtfv5dketh4hcq@art_vandelay>
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@gmail.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. And should I drop patches from
v1 already pulled in drm-next?
Thanks, Cihangir
>
> Thanks,
>
> Sean
>
next prev parent reply other threads:[~2017-08-10 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1502367012-9417-1-git-send-email-cakturk@gmail.com>
2017-08-10 12:10 ` [PATCH v2 21/29] drm/rockchip: switch to drm_*_get(), drm_*_put() helpers Cihangir Akturk
2017-08-10 18:16 ` Sean Paul
2017-08-10 19:52 ` Cihangir Akturk [this message]
2017-08-10 19:55 ` Sean Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170810195246.GA951@mbp \
--to=cakturk@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.com \
--cc=seanpaul@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox