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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4BE3BC4332F for ; Tue, 8 Nov 2022 09:49:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233736AbiKHJtu (ORCPT ); Tue, 8 Nov 2022 04:49:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60994 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233762AbiKHJtt (ORCPT ); Tue, 8 Nov 2022 04:49:49 -0500 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA55DE4 for ; Tue, 8 Nov 2022 01:49:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1667900988; x=1699436988; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=iC+onxNy7KNgKEzOFYTssykgkV5jyGSsB6F/1ba4UZ0=; b=VmZwpVODJbAWMxsVheh8gZwI0nRY3kfIqAyFjBhRReNZky9g/Gs0E3zN GhrO67dBkPMEK4RfutACZJ38aEXu01R8R82sXEnUjXyxwYiJsR34i2EZb 0vALxX8V7bZ6wEtBpuH5rVR7YAmTQjx7vk9ljyENZmo7JP1kaH5EqTDsw O538kSma9MVgvG3tbWE2jmxoi6f5CyCpi55JGx3Bgfu+uHmaU8k7hopun TAskVrZyCGDZDf8yg9KXVib9icB+3DFoCVEPbuIP1/4y687DaC5ajjlkU VZoPyLFuflVOYNgbwYwzNJSoRpvvCnHM22JoZX494kzhjXqQBZXjumsUo Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10524"; a="312445512" X-IronPort-AV: E=Sophos;i="5.96,147,1665471600"; d="scan'208";a="312445512" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Nov 2022 01:49:48 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10524"; a="811182308" X-IronPort-AV: E=Sophos;i="5.96,147,1665471600"; d="scan'208";a="811182308" Received: from shylandx-mobl2.ger.corp.intel.com (HELO [10.213.210.50]) ([10.213.210.50]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Nov 2022 01:49:46 -0800 Message-ID: Date: Tue, 8 Nov 2022 09:49:45 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.3 Subject: Re: [PATCH 1/3] Documentation/gpu: Fix section in the wrong scope Content-Language: en-US To: Lucas De Marchi , dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, linux-doc@vger.kernel.org Cc: Mauro Carvalho Chehab References: <20221107173209.2219571-1-lucas.demarchi@intel.com> <20221107173209.2219571-2-lucas.demarchi@intel.com> From: Tvrtko Ursulin Organization: Intel Corporation UK Plc In-Reply-To: <20221107173209.2219571-2-lucas.demarchi@intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On 07/11/2022 17:32, Lucas De Marchi wrote: > That section should still be inside "DRM client usage stats" rather than > as a sibling. > > Signed-off-by: Lucas De Marchi > --- > Documentation/gpu/drm-usage-stats.rst | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/Documentation/gpu/drm-usage-stats.rst b/Documentation/gpu/drm-usage-stats.rst > index 92c5117368d7..b46327356e80 100644 > --- a/Documentation/gpu/drm-usage-stats.rst > +++ b/Documentation/gpu/drm-usage-stats.rst > @@ -126,7 +126,6 @@ percentage utilization of the engine, whereas drm-engine- only reflects > time active without considering what frequency the engine is operating as a > percentage of it's maximum frequency. > > -=============================== > Driver specific implementations > =============================== > Oops - yep. Reviewed-by: Tvrtko Ursulin Regards, Tvrtko