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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E8393C433F5 for ; Thu, 28 Oct 2021 09:16:56 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 74CD460724 for ; Thu, 28 Oct 2021 09:16:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 74CD460724 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=lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id CA53B6E939; Thu, 28 Oct 2021 09:16:55 +0000 (UTC) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by gabe.freedesktop.org (Postfix) with ESMTPS id 17FDA6E939 for ; Thu, 28 Oct 2021 09:16:55 +0000 (UTC) X-IronPort-AV: E=McAfee;i="6200,9189,10150"; a="230312133" X-IronPort-AV: E=Sophos;i="5.87,189,1631602800"; d="scan'208";a="230312133" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2021 02:16:54 -0700 X-IronPort-AV: E=Sophos;i="5.87,189,1631602800"; d="scan'208";a="487056454" Received: from djustese-mobl.ger.corp.intel.com (HELO localhost) ([10.249.254.12]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2021 02:16:51 -0700 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20211028075155.02825f86@canb.auug.org.au> References: <20210122115918.63b56fa1@canb.auug.org.au> <20210122182946.6beb10b7@canb.auug.org.au> <163533676481.68716.4009950051571709814@jlahtine-mobl.ger.corp.intel.com> <20211028075155.02825f86@canb.auug.org.au> Subject: Re: linux-next: build warning after merge of the drm tree Cc: "Nikula, Jani" , Daniel Vetter , Rodrigo Vivi , Tvrtko Ursulin , Dave Airlie , DRI , Linux Next Mailing List , Linux Kernel Mailing List , Chris Wilson From: Joonas Lahtinen To: Stephen Rothwell Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Message-ID: <163541260904.5162.14679444275127334752@jlahtine-mobl.ger.corp.intel.com> User-Agent: alot/0.8.1 Date: Thu, 28 Oct 2021 12:16:49 +0300 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Quoting Stephen Rothwell (2021-10-27 23:51:55) > Hi Joonas, >=20 > On Wed, 27 Oct 2021 15:12:44 +0300 Joonas Lahtinen wrote: > > > > We should be now good to go and add drm-intel-gt-next to linux-next. > >=20 > > The branch would be as follows: > >=20 > > drm-intel-gt-next git://anongit.freedesktop.org/drm-intel for-linux= -next-gt > >=20 > > Notice the "-gt" and the end of the for-linux-next branch name. This sh= ould eliminate > > the gap we have been having. >=20 > I have added it to linux-next from today. Thanks! > I called it just > "drm-intel-gt" for consistency with the other drm trees in linux-next. We use the drm-intel-gt-next as the branch name in repo and DIM tolling, so= if we are after consistenty consistency, using the full name probably makes sense. drm-intel-gt-next for name keeps open the option for separating the drm-intel-gt-fixes too, if we decide to do so in the future. > Currently I just have you listed as a contact, is there anyone else (or > a list) that I should add? Please do add Tvrtko (Cc'd). I guess it might make sense adding Jani and Rodrigo too, as backups. Similarly Tvrtko could be added to the other drm-intel-* trees. Doesn't hurt to have more eyes especially if some folks are on a vacation. Regards, Joonas > Thanks for adding your subsystem tree as a participant of linux-next. As > you may know, this is not a judgement of your code. The purpose of > linux-next is for integration testing and to lower the impact of > conflicts between subsystems in the next merge window.=20 >=20 > You will need to ensure that the patches/commits in your tree/series have > been: > * submitted under GPL v2 (or later) and include the Contributor's > Signed-off-by, > * posted to the relevant mailing list, > * reviewed by you (or another maintainer of your subsystem tree), > * successfully unit tested, and=20 > * destined for the current or next Linux merge window. >=20 > Basically, this should be just what you would send to Linus (or ask him > to fetch). It is allowed to be rebased if you deem it necessary. >=20 > --=20 > Cheers, > Stephen Rothwell=20 > sfr@canb.auug.org.au >=20 > --=20 > Cheers, > Stephen Rothwell