Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2394010pxb; Fri, 29 Oct 2021 00:00:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzh50dFXi9xMf3Bk2qpgSIHU6Zu21EDDGzoAt/8WEGsF5xo6YXb2QAqsC1kTsmro2xQcdjX X-Received: by 2002:a17:90a:ce13:: with SMTP id f19mr9795123pju.151.1635490806731; Fri, 29 Oct 2021 00:00:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635490806; cv=none; d=google.com; s=arc-20160816; b=Q9SnJcEgwCFBS/5kOeFfNQBSJWVndHyyKH2QAXgW9iV4Z6NOjsixhczkQPYqfzgKHR 4ZVO9ksSRVMrMIpLxjNNhd8mS10oGIv6Pq59ItKBaA+IwwT8PbZst34XyTixySg2+wxj j6zgdniVMlJP04MDKA17+iNcbirKMfP5pnYVSI7BcmxR5wgSe5UVuWyzFfmFf59JHTG/ uv2EjITf0CqZRgCmUgxcybNMK2feK/kduBcR2XUIGf9C/Z1GJs+Q1l+93YnIbHcrhcfG z7K2ApkgOLoL6IJvA0b3+vmnms4DINKUd4YEhIGpce8+Q9Md+7T5i4kt2VQa+HzuW885 easw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:date:user-agent:message-id:organization:subject :from:cc:to:references:in-reply-to:content-transfer-encoding :mime-version; bh=yPCR/JYunwB5jnXLXbKatsjZnw4nfwLyxc/TGmfev+8=; b=jNZ4OFFvArWM0Uccmix7nKPmDMNHiWUw6Y5I0wbDpymNdNIARTAklhF2DUh3sLWguh WqKtQW44lYE134IXldmwXPuYDMT7GBLFboA80X+AXoLjFRLSKnaQSmJIexfi5nndB7+T /xYjT1yQZskQF1e0gYfcqO2yYWVRcQbIpf1kaPefnVY+Dlf/+GMEnKI0G/rPeHeIHYzv p6eZG7UEkCitYycCdtx7r82aROEzCy3scB5bZf8gczz7cB9sGvDDMwhWYbOHTzP3D39y uFuZuTYF40QVBBnAn5tkDxAd7WrM5SsglHt5iSPSH2nQO2oN+TzB9FaoWPGX+WztnniK OWqw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id nl6si6429636pjb.171.2021.10.28.23.59.53; Fri, 29 Oct 2021 00:00:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232108AbhJ2HBZ convert rfc822-to-8bit (ORCPT + 99 others); Fri, 29 Oct 2021 03:01:25 -0400 Received: from mga17.intel.com ([192.55.52.151]:55284 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230252AbhJ2HBY (ORCPT ); Fri, 29 Oct 2021 03:01:24 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10151"; a="211375315" X-IronPort-AV: E=Sophos;i="5.87,191,1631602800"; d="scan'208";a="211375315" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2021 23:52:20 -0700 X-IronPort-AV: E=Sophos;i="5.87,191,1631602800"; d="scan'208";a="448274796" Received: from shishpan-mobl2.ccr.corp.intel.com (HELO localhost) ([10.249.254.23]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2021 23:52:18 -0700 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT In-Reply-To: <20211029114840.6a3a78bd@canb.auug.org.au> References: <20211029114840.6a3a78bd@canb.auug.org.au> To: DRI , Dave Airlie , Stephen Rothwell Cc: John Harrison , Linux Kernel Mailing List , Linux Next Mailing List , Matthew Brost From: Joonas Lahtinen Subject: Re: linux-next: manual merge of the drm tree with Linus' tree Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Message-ID: <163549033603.4317.6416900804800927743@jlahtine-mobl.ger.corp.intel.com> User-Agent: alot/0.8.1 Date: Fri, 29 Oct 2021 09:52:16 +0300 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Stephen Rothwell (2021-10-29 03:48:40) > Hi all, > > Today's linux-next merge of the drm tree got a conflict in: > > drivers/gpu/drm/i915/i915_trace.h > > between commit: > > 9a4aa3a2f160 ("drm/i915: Revert 'guc_id' from i915_request tracepoint") > > from Linus' tree and commit: > > 3cb3e3434b9f ("drm/i915/guc: Move fields protected by guc->contexts_lock into sub structure") > > from the drm tree. > > I fixed it up (I used the former version) and can carry the fix as > necessary. The resolution for the conflict is to drop the guc_id field completely in linux-next. Regards, Joonas > This is now fixed as far as linux-next is concerned, but any > non trivial conflicts should be mentioned to your upstream maintainer > when your tree is submitted for merging. You may also want to consider > cooperating with the maintainer of the conflicting tree to minimise any > particularly complex conflicts. > > -- > Cheers, > Stephen Rothwell