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 B0624C001DE for ; Fri, 28 Jul 2023 08:11:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234650AbjG1ILn (ORCPT ); Fri, 28 Jul 2023 04:11:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50888 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234786AbjG1ILX (ORCPT ); Fri, 28 Jul 2023 04:11:23 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e5ab]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DA50635A2 for ; Fri, 28 Jul 2023 01:11:10 -0700 (PDT) Received: from [192.168.1.100] (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id 0BA0F6607166; Fri, 28 Jul 2023 09:11:09 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1690531869; bh=yYvD8O4U9F8BRRQYpZMS0nxYKjHuhUsKk66nJf/o4K4=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=PHxGpKjauUYQ+IRh+pFphVXTu+e4qLGhqkzO9B9n72R7UWmSP7Ty3QtoQjBnur7Xm 4qDtxsdoAXvlXlqDQ/Zp5MCgFlqIBEDorPx0iNGIguKfoYgn34i9EggXOSzD3ZWHWz Qd2CBe/ojBoYPn24B1e9qga4uj+kM7qJGlxu7tNY4W4jNDULZpT5FeuOtmgCqNwNcn V7DSZ5Coz8ukTktW/KI0r3yoTc9eBbMMuPTGIgOz+ENl3MnVM1kp1iaTkuysjQtaBm 563yHj5s8r1pxW+0TAE/VycPajQqcuGlAEdz64BsW1EJADolN323rlgmkInxvc3CPb D0Kgh27k4JCNQ== Message-ID: <8c18da20-87cb-4125-c93a-c6750fd02b7d@collabora.com> Date: Fri, 28 Jul 2023 10:11:06 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [PATCH v7 2/4] drm/mediatek: Fix using wrong drm private data to bind mediatek-drm Content-Language: en-US To: "Jason-JH.Lin" , Chun-Kuang Hu Cc: Matthias Brugger , Jason-ch Chen , Johnson Wang , Singo Chang , Nancy Lin , Shawn Sung , dri-devel@lists.freedesktop.org, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Project_Global_Chrome_Upstream_Group@mediatek.com References: <20230727164114.20638-1-jason-jh.lin@mediatek.com> <20230727164114.20638-3-jason-jh.lin@mediatek.com> From: AngeloGioacchino Del Regno In-Reply-To: <20230727164114.20638-3-jason-jh.lin@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 27/07/23 18:41, Jason-JH.Lin ha scritto: > Add checking the length of each data path before assigning drm private > data into all_drm_priv array. > > Fixes: 1ef7ed48356c ("drm/mediatek: Modify mediatek-drm for mt8195 multi mmsys support") > Signed-off-by: Jason-JH.Lin Reviewed-by: AngeloGioacchino Del Regno