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 A8C5BC433F5 for ; Tue, 12 Oct 2021 10:35:46 +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 3CD3161039 for ; Tue, 12 Oct 2021 10:35:46 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 3CD3161039 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=emersion.fr 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 AB4D96E8E2; Tue, 12 Oct 2021 10:35:44 +0000 (UTC) Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136]) by gabe.freedesktop.org (Postfix) with ESMTPS id 0EEAB6E8E2 for ; Tue, 12 Oct 2021 10:35:43 +0000 (UTC) Date: Tue, 12 Oct 2021 10:35:37 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emersion.fr; s=protonmail; t=1634034940; bh=Se2A40hn6I4G+AuhxZClaT3FV18pJ0SfX4EJ5oqmlpA=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=IkGogsBlGDiz3l3ArV7s7FpBRvFCFdOLIm0aHBri7MSkraYQECr9XjeXnvEYaX29G HhXf6QPSX2Sv/YV2gaS1lQMRQMe26+c/eVuyDY3i4AnGF22jb8u5epCLpn9IoMKMVa dJFyU/f4I3K8cMDVHSljUZnJU53v2vh3JWd8LhzQ/VFf1h2GPdGOkqZe0N0MBQJRCd hqQ8Gn9xMUFwgpWeCmczxiEkxBWVRsiUF3qyJ6uVo+HFGFrHGRaU3BnXx0YBk0LAKX jF6IBuheB4ZwgLuyRH0RrMQCZbb8EZUsFNV8dDXaYkAEnkOsJth0rURPJvOOQiwExf 3s2W+nOFWf26A== To: Pekka Paalanen From: Simon Ser Cc: Uma Shankar , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, harry.wentland@amd.com, ville.syrjala@linux.intel.com, brian.starkey@arm.com, sebastian@sebastianwick.net, Shashank.Sharma@amd.com Subject: Re: [RFC v2 01/22] drm: RFC for Plane Color Hardware Pipeline Message-ID: In-Reply-To: <20211006155559.606521de@eldfell> References: <20210906213904.27918-1-uma.shankar@intel.com> <20210906213904.27918-2-uma.shankar@intel.com> <20211006155559.606521de@eldfell> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: , Reply-To: Simon Ser Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Tuesday, October 12th, 2021 at 12:30, Pekka Paalanen wrote: > is there a practise of landing proposal documents in the kernel? How > does that work, will a kernel tree carry the patch files? > Or should this document be worded like documentation for an accepted > feature, and then the patches either land or don't? Once everyone agrees, the RFC can land. I don't think a kernel tree is necessary. See: https://dri.freedesktop.org/docs/drm/gpu/rfc/index.html 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 0F60FC433EF for ; Tue, 12 Oct 2021 10:35:52 +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 BA4D0610A3 for ; Tue, 12 Oct 2021 10:35:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org BA4D0610A3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=emersion.fr 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 608F86E8E4; Tue, 12 Oct 2021 10:35:45 +0000 (UTC) Received: from mail-4018.proton.ch (mail-4018.proton.ch [185.70.40.18]) by gabe.freedesktop.org (Postfix) with ESMTPS id 3A9A16E8E4 for ; Tue, 12 Oct 2021 10:35:43 +0000 (UTC) Date: Tue, 12 Oct 2021 10:35:37 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emersion.fr; s=protonmail; t=1634034940; bh=Se2A40hn6I4G+AuhxZClaT3FV18pJ0SfX4EJ5oqmlpA=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=IkGogsBlGDiz3l3ArV7s7FpBRvFCFdOLIm0aHBri7MSkraYQECr9XjeXnvEYaX29G HhXf6QPSX2Sv/YV2gaS1lQMRQMe26+c/eVuyDY3i4AnGF22jb8u5epCLpn9IoMKMVa dJFyU/f4I3K8cMDVHSljUZnJU53v2vh3JWd8LhzQ/VFf1h2GPdGOkqZe0N0MBQJRCd hqQ8Gn9xMUFwgpWeCmczxiEkxBWVRsiUF3qyJ6uVo+HFGFrHGRaU3BnXx0YBk0LAKX jF6IBuheB4ZwgLuyRH0RrMQCZbb8EZUsFNV8dDXaYkAEnkOsJth0rURPJvOOQiwExf 3s2W+nOFWf26A== To: Pekka Paalanen From: Simon Ser Cc: Uma Shankar , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, harry.wentland@amd.com, ville.syrjala@linux.intel.com, brian.starkey@arm.com, sebastian@sebastianwick.net, Shashank.Sharma@amd.com Message-ID: In-Reply-To: <20211006155559.606521de@eldfell> References: <20210906213904.27918-1-uma.shankar@intel.com> <20210906213904.27918-2-uma.shankar@intel.com> <20211006155559.606521de@eldfell> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Intel-gfx] [RFC v2 01/22] drm: RFC for Plane Color Hardware Pipeline X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Simon Ser Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Tuesday, October 12th, 2021 at 12:30, Pekka Paalanen wrote: > is there a practise of landing proposal documents in the kernel? How > does that work, will a kernel tree carry the patch files? > Or should this document be worded like documentation for an accepted > feature, and then the patches either land or don't? Once everyone agrees, the RFC can land. I don't think a kernel tree is necessary. See: https://dri.freedesktop.org/docs/drm/gpu/rfc/index.html