Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1624732yba; Thu, 25 Apr 2019 03:02:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqwBJrBKZtFjgHRkJzdzUsQEILOMAJw7WIeztGOS84p3QpSGg+ldZofLWF0gBF3mLZm9Lr+l X-Received: by 2002:a63:541d:: with SMTP id i29mr7949053pgb.174.1556186550663; Thu, 25 Apr 2019 03:02:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556186550; cv=none; d=google.com; s=arc-20160816; b=batXT41FvJhNtqmrxAifCCn3M0zM5MyVSJMgLOXbA4uqf9sN0JoigHNqX30WtMY6jH VP9aFwXXM0az53OFsqIM0Oiyorp/dGBl9vBwHEfK0/f+kBbhNF0Ye1OYI1Bm+q62dyIt 3FO/fIhN8jUZG+HuFvkIuImaoKophReAUfqxiiTM10PiqjYEYc3SlSdhde4yhzUZ37Te rHPDO6JVZSQVITfT9dHyrH4PrU+lpynCVTbeaJ/cDDzTdfdWLckCaaCuCyXm+0VSoYbL qfM1BCExqeF0UypJ7Je1nGwG1SwQr0OnhAtb1v9ghwcs9wq07L9NVBwQiykfNpmNJDVy to0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=hX+B32gMQJz2smfn6W3bHsZFJwgmnoUaBrBOnw0D9gI=; b=O7ykXfCz3ddYzLjfRYLFX8JcMsCqfrCK59maZgQfFaicuI55/RCuiNfpfTbl25DsW8 WY9MG0kgE/Sl41JtI5v7+vPNQ+huCE5SM0NTZ+MsPVrg4MfGgu+wS3fc+iEX+3Yj/dO8 6QXvmOhrPbQmZ240Db8CH5onNt/OtqPEjeGgTr/BylG0tRLhWrsvfLVUQ/zBuoWJiz6/ ZMvI9lVPktaKfLsKzgHWv2CkxuE9AS2hzCA8/E1EhfYSbJxCSWnIdJZ7YJzXZsU/DvSv LEMaFmGuaiuIqdF7tQcpr/872Ws9TpJ1cai7tQ1H0Ojotxxvx019i7ILCCvRN5THb4Es /nlQ== ARC-Authentication-Results: i=1; mx.google.com; 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 d2si19840709pgv.22.2019.04.25.03.02.13; Thu, 25 Apr 2019 03:02:30 -0700 (PDT) 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; 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 S2388182AbfDXS4Y (ORCPT + 99 others); Wed, 24 Apr 2019 14:56:24 -0400 Received: from anholt.net ([50.246.234.109]:40302 "EHLO anholt.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388098AbfDXS4V (ORCPT ); Wed, 24 Apr 2019 14:56:21 -0400 Received: from localhost (localhost [127.0.0.1]) by anholt.net (Postfix) with ESMTP id 9736910A3399; Wed, 24 Apr 2019 11:56:20 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at anholt.net Received: from anholt.net ([127.0.0.1]) by localhost (kingsolver.anholt.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QLcSsQefhvOA; Wed, 24 Apr 2019 11:56:18 -0700 (PDT) Received: from eliezer.anholt.net (localhost [127.0.0.1]) by anholt.net (Postfix) with ESMTP id EA1BF10A33B6; Wed, 24 Apr 2019 11:56:17 -0700 (PDT) Received: by eliezer.anholt.net (Postfix, from userid 1000) id 3C77A2FE3AA9; Wed, 24 Apr 2019 11:56:17 -0700 (PDT) From: Eric Anholt To: dri-devel@lists.freedesktop.org, Dave Airlie Cc: linux-kernel@vger.kernel.org, Eric Anholt Subject: [PATCH 1/2] drm/doc: Allow new UAPI to be used once it's in the driver's -next. Date: Wed, 24 Apr 2019 11:56:16 -0700 Message-Id: <20190424185617.16865-1-eric@anholt.net> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I was trying to figure out if it was permissible to merge the Mesa side of V3D's CSD support yet while it's in drm-misc-next but not drm-next, and developers on #dri-devel IRC had differing opinions of what the requirement was. Propose a clarification here to see if Dave Airlie agrees. Signed-off-by: Eric Anholt --- Personally, I thought the rule was "has to be in drm-next", but assuming our review processes aren't totally broken, this should be enough. Documentation/gpu/drm-uapi.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst index c9fd23efd957..8e5545dfbf82 100644 --- a/Documentation/gpu/drm-uapi.rst +++ b/Documentation/gpu/drm-uapi.rst @@ -92,8 +92,9 @@ leads to a few additional requirements: requirements by doing a quick fork. - The kernel patch can only be merged after all the above requirements are met, - but it **must** be merged **before** the userspace patches land. uAPI always flows - from the kernel, doing things the other way round risks divergence of the uAPI + but it **must** be merged to the driver's -next tree (as documented in + MAINTAINERS) **before** the userspace patches land. uAPI always flows from + the kernel, doing things the other way round risks divergence of the uAPI definitions and header files. These are fairly steep requirements, but have grown out from years of shared -- 2.20.1