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 87956C64EC4 for ; Thu, 9 Mar 2023 00:10:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229801AbjCIAKH (ORCPT ); Wed, 8 Mar 2023 19:10:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56588 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230102AbjCIAJh (ORCPT ); Wed, 8 Mar 2023 19:09:37 -0500 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 661D991B7C for ; Wed, 8 Mar 2023 16:08: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=1678320528; x=1709856528; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=zv20jPCINFakTYCqUmZD3EcBqCSqS/XF/HDBjCEXcqc=; b=i2JcMavLUmUu18NZd7n2t4XC+E5ZgGuoqpX7fl8KEfMRDKpX3GMLkf/w Z+BbS/TJT4JsbPliJcQbawCkKvPHBnwRp1HsrrqPqGbtQCRO+0vasbVfh 2BEr1S5kJTypPgt/eMQd804rzbjhcD3pJJbfEUH8qee4YjE0+8tkOsmEi ixo2YvaC6Qc/qdILjKB2yLgj3zGItbB9TKeT6KGCFGGn9+FZet8Mm+1P7 nE3yUCEe9iAboLoAhi1zJHQjiZXxS35RKpolq1FWm07a6RcvmPR4ya0xS T3tSpGz0jsijwpyQdyQ+KhMvIRyVeREvWzOBcrSzxrWD9YXz94SYvt5U6 Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10643"; a="401142085" X-IronPort-AV: E=Sophos;i="5.98,244,1673942400"; d="scan'208";a="401142085" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Mar 2023 16:01:01 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10643"; a="677186739" X-IronPort-AV: E=Sophos;i="5.98,244,1673942400"; d="scan'208";a="677186739" Received: from gbain-mobl1.ger.corp.intel.com (HELO intel.com) ([10.252.47.108]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Mar 2023 16:00:56 -0800 Date: Thu, 9 Mar 2023 01:00:54 +0100 From: Andi Shyti To: Andrzej Hajda Cc: Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , Tvrtko Ursulin , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Andi Shyti , Chris Wilson , Nirmoy Das Subject: Re: [PATCH v5 1/4] drm/i915/gt: make nop_clear_range public Message-ID: References: <20230308-guard_error_capture-v5-0-6d1410d13540@intel.com> <20230308-guard_error_capture-v5-1-6d1410d13540@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230308-guard_error_capture-v5-1-6d1410d13540@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Andrzej, On Wed, Mar 08, 2023 at 04:39:03PM +0100, Andrzej Hajda wrote: > Function nop_clear_range can be used instead of local implementations. > > Signed-off-by: Andrzej Hajda Reviewed-by: Andi Shyti Andi