From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EC056C43441 for ; Tue, 20 Nov 2018 09:54:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 02C3A20851 for ; Tue, 20 Nov 2018 09:53:20 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 02C3A20851 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727950AbeKTUVe (ORCPT ); Tue, 20 Nov 2018 15:21:34 -0500 Received: from mga18.intel.com ([134.134.136.126]:28551 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726943AbeKTUVd (ORCPT ); Tue, 20 Nov 2018 15:21:33 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Nov 2018 01:53:18 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,256,1539673200"; d="scan'208";a="109625618" Received: from jnikula-mobl3.fi.intel.com (HELO localhost) ([10.237.72.61]) by fmsmga001.fm.intel.com with ESMTP; 20 Nov 2018 01:53:11 -0800 From: Jani Nikula To: Fernando , Lucas Stach , dri-devel@lists.freedesktop.org Cc: Haneen Mohammed , Alexandre Belloni , Gilles Muller , David Airlie , virtualization@lists.linux-foundation.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 Ferre , Nicolas Palix , etnaviv@lists.freedesktop.org, Julia Lawall , Sean Paul , linux-arm-kernel@lists.infradead.org, Michal Marek , Boris Brezillon , linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Kieran Bingham , Shawn Guo , Laurent Pinchart Subject: Re: [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put" In-Reply-To: <1542387884.1134874.1579436592.07F916C5@webmail.messagingengine.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20181115221634.22715-1-greenfoo@gluegarage.com> <20181115221634.22715-4-greenfoo@gluegarage.com> <1542363310.23489.22.camel@pengutronix.de> <1542387884.1134874.1579436592.07F916C5@webmail.messagingengine.com> Date: Tue, 20 Nov 2018 11:53:43 +0200 Message-ID: <87lg5of520.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 16 Nov 2018, Fernando wrote: > 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? I advise most of our developers to work on drm-tip because it contains the latest stuff in drm core, i915, amd, most of the small drivers, as well as sound. It's a bit like "linux-next for graphics". And you don't really have to care about the merge cycles with that. But YMMV, it probably doesn't work for everyone. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center