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 010DFC678D5 for ; Thu, 9 Mar 2023 00:07:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230410AbjCIAH0 (ORCPT ); Wed, 8 Mar 2023 19:07:26 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49940 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230315AbjCIAHB (ORCPT ); Wed, 8 Mar 2023 19:07:01 -0500 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5212AD8853 for ; Wed, 8 Mar 2023 16:05:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1678320341; x=1709856341; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=L8mJFeEuib6omOevxs+0qneHqkgXoH+0dfoFaHakng0=; b=Cz2FYYkYUo9vHIjvQQ0yXbVvt00wLnm1xoissuk7DUN8oD/xAnUYr82R hK6GNITt82JY3b+4UW/TAWCgzc0HlKe+3ca/XRtdGasqJsVBxUnF6DVQ5 KWWoCl9fJ2XqFhGoh5tajsM72AHHqG6IHXkSWByCGVlI/sbcrEcgUz8VW Wo5w/L/KnyDNFUFWXpkRK8ofK8P1n2UxUGi8dHZPr4ySPpRFvgtl8Tltm JUE811gLboC1YzB+iJIv2/E0OeAXw8UZXu9Fr+1sDXcCWv8cwoWdQ9cva 2+ASzVs55B3NoBV3qJYvXVOWZ2cTbNDXb7B9a3OXhESkhOViN2ndBncqq A==; X-IronPort-AV: E=McAfee;i="6500,9779,10643"; a="398890705" X-IronPort-AV: E=Sophos;i="5.98,244,1673942400"; d="scan'208";a="398890705" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Mar 2023 16:01:55 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10643"; a="766202216" X-IronPort-AV: E=Sophos;i="5.98,244,1673942400"; d="scan'208";a="766202216" Received: from gbain-mobl1.ger.corp.intel.com (HELO intel.com) ([10.252.47.108]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Mar 2023 16:01:42 -0800 Date: Thu, 9 Mar 2023 01:01:39 +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 2/4] drm/i915/display: use nop_clear_range instead of local function Message-ID: References: <20230308-guard_error_capture-v5-0-6d1410d13540@intel.com> <20230308-guard_error_capture-v5-2-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-2-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:04PM +0100, Andrzej Hajda wrote: > Since nop_clear_range is visible it can be used here. > > Signed-off-by: Andrzej Hajda Reviewed-by: Andi Shyti Thanks, Andi