Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp724421imu; Fri, 16 Nov 2018 09:12:50 -0800 (PST) X-Google-Smtp-Source: AJdET5fajokYlh2njziVHO+l+CfkRuL1kaVlYq1m1Yq53ZxlrIKMeVGMGHmKlsLyZ4C8gxqyaU3X X-Received: by 2002:a63:441e:: with SMTP id r30mr10877864pga.128.1542388370285; Fri, 16 Nov 2018 09:12:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542388370; cv=none; d=google.com; s=arc-20160816; b=iFZZqKklCCBDZCwh1ayzBU/sgo6hVAGqZojANrjPsG++S0ftz33AObRkHxXaa0Uf8F 60isnHfka+IQ7/deLjVy95+QCEDxLL7U6R8IEf6aGIvLNP1tHEvfoLcTMF8QZsDHhJPL yGlwr5/Zp2Py13jNcvWUW8pdRN/nFwolrsutmBZar+hSAMXIUlglrA5RJzhvGHt5Ptaf aK0t0OsDJdiewZ+rakE8dG7deoZ/hBAxpPv9DHHFviD6dcOvyghfWv4GJCHKqRkqDZqf g4unxtqyKeH7chNqh9lygKkoxERDZ5TqHoI8z0gatWM7HqIPinYSE5HiXNGgA3hjJWa9 CVZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:subject:references:in-reply-to :content-transfer-encoding:mime-version:cc:to:from:message-id :dkim-signature:dkim-signature; bh=iEGdTKyN0HEwE030k1fx6PVMxlh7yAiD+wyouNJIlik=; b=l371TX9hVtyEWzpjsRbI5iUcgCwYaWeNAqBOGvc/HQJC3oJyu8ML1wV0l/XkbFcrhU 9zn4lHiFpjEbZGa+M1T5zolNe07X0MPCnj3B9Aba46VLwUNpW1LpazPPtfOwfoJIukgW 3Luh32X2BVAuYMPbyrWNcTLTqNKdVky0ZT21/2+hzYhSqy3pQCFjpRFTeM77wSZC/8ge jsuQa90dmhnJys+NkWsxFJnpDgXt+LbG38lz4DZNbq/8Bg79TebKZAXn0drB8NYjDnmE KKbfUCi2vXuablg+d43fJSQETH5/wEFihIWufFdpWzTfR5mjpgmIKomale6lIXj94c3W wS2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gluegarage.com header.s=mesmtp header.b=cyUwKVp4; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=TvMqoVHm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u11-v6si30411816pgh.55.2018.11.16.09.12.34; Fri, 16 Nov 2018 09:12:50 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gluegarage.com header.s=mesmtp header.b=cyUwKVp4; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=TvMqoVHm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729265AbeKQDZK (ORCPT + 99 others); Fri, 16 Nov 2018 22:25:10 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:35853 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728195AbeKQDZK (ORCPT ); Fri, 16 Nov 2018 22:25:10 -0500 X-Greylist: delayed 429 seconds by postgrey-1.27 at vger.kernel.org; Fri, 16 Nov 2018 22:25:09 EST Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1BAED21F39; Fri, 16 Nov 2018 12:04:49 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute1.internal (MEProxy); Fri, 16 Nov 2018 12:04:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gluegarage.com; h=message-id:from:to:cc:mime-version:content-transfer-encoding :content-type:in-reply-to:references:subject:date; s=mesmtp; bh= iEGdTKyN0HEwE030k1fx6PVMxlh7yAiD+wyouNJIlik=; b=cyUwKVp4MdK08Lna xA0UnRWQ4ny7nhvCNYO4ryjuJLbeRvlSnGqpScytgY4Jk6L4p6plJ3+owtNhYbAO 8IMaADYqoeA0EqjugizbwV1rCougjvSQnd57LjQFwrLfyTsdZza/akb3SqUFTdH/ cqyWc7ZaViHFA6ZnsUeY3dnoA5M= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=iEGdTKyN0HEwE030k1fx6PVMxlh7yAiD+wyouNJIl ik=; b=TvMqoVHm4ale8vgWSzOWXPcYQJPgTzekqaXPgUJ1GtU8T7dZ2nUtvz34H wdVxDRHT57D3WiB2vuTAumn9elnRIzriDcQ7GdvLElvBfaQMFjGH1Pj9QdCWftEv KtrJ4aZJjTa14B5nxUVckNObFRqRvBTeU3Kb8u4IsJlKqwHyd53Rs7Gglu9j1uyM B3LvvjZNMpKK6ounVGWBNznessBLu1mV2Oc99wkuh1r9gkdgXuEONCrWvcjIWFJp IDqPGXJVyy3Q1FpnARyKUdIYWeo84StNPzJDs6VK4WdH83IoEq8rqFn+DrppT5e5 HyQERmyO6AOWNj5f25W2LfpBV3Eaw== X-ME-Sender: X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 51F4741E7; Fri, 16 Nov 2018 12:04:44 -0500 (EST) Message-Id: <1542387884.1134874.1579436592.07F916C5@webmail.messagingengine.com> From: Fernando To: Lucas Stach , dri-devel@lists.freedesktop.org Cc: Haneen Mohammed , Alexandre Belloni , Gilles Muller , David Airlie , linux-kernel@vger.kernel.org, Gerd Hoffmann , cocci@systeme.lip6.fr, Marek Vasut , Jonathan Corbet , linux-doc@vger.kernel.org, Alexey Brodkin , Maxime Ripard , Ludovic Desroches , Russell King , Nicolas Palix , etnaviv@lists.freedesktop.org, Julia Lawall , virtualization@lists.linux-foundation.org, Sean Paul , linux-arm-kernel@lists.infradead.org, Michal Marek , Boris Brezillon , Nicolas Ferre , linux-renesas-soc@vger.kernel.org, Kieran Bingham , Shawn Guo , Laurent Pinchart MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-2d882eb6 In-Reply-To: <1542363310.23489.22.camel@pengutronix.de> References: <20181115221634.22715-1-greenfoo@gluegarage.com> <20181115221634.22715-4-greenfoo@gluegarage.com> <1542363310.23489.22.camel@pengutronix.de> Subject: Re: [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put" Date: Fri, 16 Nov 2018 18:04:44 +0100 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > >=20 > > > Signed-off-by: Fernando Ramos > > --- > > =C2=A0drivers/gpu/drm/arc/arcpgu_drv.c=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0| 4 ++-- > > =C2=A0drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 4 ++-- > > =C2=A0drivers/gpu/drm/etnaviv/etnaviv_drv.c=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0| 4 ++-- >=20 > At least the etnaviv part of the patch is already fixed in linux-next. >=20 > Regards, > Lucas =20 Thanks for the notice. I'm new on this, how should I proceed? Should I create a new (V2) patch ser= ies 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!