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 X-Spam-Level: X-Spam-Status: No, score=-11.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C45D0C64E7A for ; Tue, 24 Nov 2020 13:02:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 739232076E for ; Tue, 24 Nov 2020 13:02:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="Sz5yMIkU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387822AbgKXNC1 (ORCPT ); Tue, 24 Nov 2020 08:02:27 -0500 Received: from mail.kernel.org ([198.145.29.99]:59712 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387663AbgKXNC1 (ORCPT ); Tue, 24 Nov 2020 08:02:27 -0500 Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2FBE620857 for ; Tue, 24 Nov 2020 13:02:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606222946; bh=mRyFh67kJfy8ZITfHjrOgCZZLf01NwP2u0w2OlFgRgg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Sz5yMIkUhhtWCOgnTOr5d0bv8kSWhD3qN0uSJ43dioTwPSv0d9TuB5GEqDbC9qkdx l/igfcndpP0AI6ItVUWKeXoLPryk7PO33BV3QUErLEuMwflWwd6gTzfUeJyHounyqB HPdA5dFCj3LRBEFxtOEicfcHfJ+4YxMWJJOzJbTc= Received: by mail-oi1-f176.google.com with SMTP id s18so22527311oih.1 for ; Tue, 24 Nov 2020 05:02:26 -0800 (PST) X-Gm-Message-State: AOAM533LyT+w/74RiNkuZDs4Y8f6RYW5pkLnLomQjH2pdRi8ML9oWJli MEMoEKVtSpfLrjvYNf+2O+t3ylyLkDmGsucyGQE= X-Google-Smtp-Source: ABdhPJwd4HlK8aErAo0yZOEzAhlqNo8LDzc3+z00A1haMLZdh7R8bcKiStZxVrkCerFt2PktDuPW2+m1X4yfqNMJ5p0= X-Received: by 2002:aca:3c54:: with SMTP id j81mr2648803oia.11.1606222945358; Tue, 24 Nov 2020 05:02:25 -0800 (PST) MIME-Version: 1.0 References: <1606197161-25976-1-git-send-email-rajan.vaja@xilinx.com> In-Reply-To: From: Arnd Bergmann Date: Tue, 24 Nov 2020 14:02:09 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] firmware: xilinx: Use hash-table for api feature check To: Michal Simek Cc: Rajan Vaja , Arnd Bergmann , Linux ARM , "linux-kernel@vger.kernel.org" , TEJASP@xilinx.com, Amit Sunil Dhamne , Ravi Patel Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 24, 2020 at 1:54 PM Michal Simek wrote: > On 24. 11. 20 6:52, Rajan Vaja wrote: > > Some lines should be added. > > Cc: stable > Fixes: f3217d6f2f7a ("firmware: xilinx: fix out-of-bounds access") > > Tested-by: Michal Simek Reviewed-by: Arnd Bergmann > Arnd: do you see any issue with this? > I found that your origin patch was taken by Greg and pushed to any > 5.10-rc version which caused panic on Xilinx Versal. That's why I would > like to get this patch to v5.10 if possible. Looks ok to me. If you'd like me to pick it up through the soc fixes branch, please forward with the above tags to soc@kernel.org Arnd