[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1542387884.1134874.1579436592.07F916C5@webmail.messagingengine.com>
Date: Fri, 16 Nov 2018 18:04:44 +0100
From: Fernando <greenfoo@...egarage.com>
To: Lucas Stach <l.stach@...gutronix.de>,
dri-devel@...ts.freedesktop.org
Cc: Haneen Mohammed <hamohammed.sa@...il.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Gilles Muller <Gilles.Muller@...6.fr>,
David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
Gerd Hoffmann <kraxel@...hat.com>, cocci@...teme.lip6.fr,
Marek Vasut <marex@...x.de>, Jonathan Corbet <corbet@....net>,
linux-doc@...r.kernel.org, Alexey Brodkin <abrodkin@...opsys.com>,
Maxime Ripard <maxime.ripard@...tlin.com>,
Ludovic Desroches <ludovic.desroches@...rochip.com>,
Russell King <linux+etnaviv@...linux.org.uk>,
Nicolas Palix <nicolas.palix@...g.fr>,
etnaviv@...ts.freedesktop.org, Julia Lawall <Julia.Lawall@...6.fr>,
virtualization@...ts.linux-foundation.org,
Sean Paul <sean@...rly.run>,
linux-arm-kernel@...ts.infradead.org,
Michal Marek <michal.lkml@...kovi.net>,
Boris Brezillon <boris.brezillon@...tlin.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
linux-renesas-soc@...r.kernel.org,
Kieran Bingham <kieran.bingham+renesas@...asonboard.com>,
Shawn Guo <shawnguo@...nel.org>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put"
On Fri, Nov 16, 2018, at 11:15 AM, Lucas Stach wrote:
> Am Donnerstag, den 15.11.2018, 23:16 +0100 schrieb Fernando Ramos:
> > This patch unifies the naming of DRM functions for reference counting as
> > requested on Documentation/gpu/todo.rst
> >
> > > Signed-off-by: Fernando Ramos <greenfoo@...egarage.com>
> > ---
> > drivers/gpu/drm/arc/arcpgu_drv.c | 4 ++--
> > drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 4 ++--
> > drivers/gpu/drm/etnaviv/etnaviv_drv.c | 4 ++--
>
> At least the etnaviv part of the patch is already fixed in linux-next.
>
> Regards,
> Lucas
Thanks for the notice.
I'm new on this, how should I proceed? Should I create a new (V2) patch series with these changes reverted? Or will the maintainer automatically take care of this when merging?
And, related to this, what is the "good" branch to start developing new drm patches? Is is "drm-next" or "linux-next"? Or does it change depending on how much time until the merge window closes?
Thanks!
Powered by blists - more mailing lists