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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A9C48C43217 for ; Tue, 16 Nov 2021 15:43:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9502663214 for ; Tue, 16 Nov 2021 15:43:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238532AbhKPPqD (ORCPT ); Tue, 16 Nov 2021 10:46:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56796 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238551AbhKPPpT (ORCPT ); Tue, 16 Nov 2021 10:45:19 -0500 Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 98181C061210 for ; Tue, 16 Nov 2021 07:42:19 -0800 (PST) Received: by mail-wr1-x429.google.com with SMTP id d27so38490752wrb.6 for ; Tue, 16 Nov 2021 07:42:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=MaOSO/5HtReWKBBksqBOQJDhfTRE2n/pBGJORKYgmI8=; b=dpMihBVSiTIhJ8gwEIK/0RaxfyXs2DtvxfMOWHwvsfqgQpUny0lQtED0wIphEPCb6v AEzTzY5KUWh+ZBUlwhm1MKOSsfEKvWzAZN6hA0iVz1ZkNSHET0GNQ7X4qOZ4ru7PoXmg a/08/a6OGQp4ufg1hfyxfYLxOjuSPoP4Iv2indtDuuY25uHOzB4zY/j/Htu2gPPN48F8 +FDsCnukvP5bxxuyqV5df/R9Dld2m5MFGmv/6quqjj8jagtwmzBL49QLLLkaiJPMV3TB utBJFccrrLjAw31i2P+rtb2jHXojpAt5V88ehKxTw8pEyulGHnLBAJQgM7JuB/O0nT8J yzQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=MaOSO/5HtReWKBBksqBOQJDhfTRE2n/pBGJORKYgmI8=; b=VAy/QMJS3PTNwk6QXYorSBCtp8A9haNIKahSY1SghCwtoiUsqLJfKm5RpVpdc4h1Mp AyAY43z03P1eV89y6kTqMpEqzovChgHcg3BiGn4RLC7TH/7rXmfKnsqHnu+zT20oaOKs 9IFVF6kca8L+LQll51xRxghDV65k5476ixV5XfWMEDr6zrt3fkbIE4TJKCdf58GOt+oO 7Y9vVpu6cAJLQbuYFH4BP7zgieTnOkrlufOGfznSbpb+4bKZv1PNDlr0x87lJxqRjibd k1dg59q48MOiObyMvSIZ1GsHjGRXIzofa6SkfhzNoU5WpSW7i6ZfZKOYACIjbNObg2hs Mh+A== X-Gm-Message-State: AOAM530HE0DML9crlZy3CYhEy3MM6lBt8/I+mzFmY7TkpbDB7+WH2v35 IFKSQ6SmOeUy+soJp5IU5sKVzA== X-Google-Smtp-Source: ABdhPJwGazAeHXqWI2KmcXg8HN2YudpmutPJQ1rdklClDDMa6uJ9nc+mW3BEpIrYrJ5e6pEnv6kpCA== X-Received: by 2002:a5d:5303:: with SMTP id e3mr10447721wrv.73.1637077337983; Tue, 16 Nov 2021 07:42:17 -0800 (PST) Received: from google.com ([95.148.6.231]) by smtp.gmail.com with ESMTPSA id q4sm17892469wrs.56.2021.11.16.07.42.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Nov 2021 07:42:17 -0800 (PST) Date: Tue, 16 Nov 2021 15:42:15 +0000 From: Lee Jones To: Daniel Thompson Cc: phone-devel@vger.kernel.org, Andy Gross , Bjorn Andersson , Rob Herring , Marijn Suijten , Jingoo Han , ~postmarketos/upstreaming@lists.sr.ht, AngeloGioacchino Del Regno , Konrad Dybcio , Martin Botka , Jami Kettunen , Pavel Dubrova , Kiran Gunda , Bryan Wu , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org Subject: Re: [PATCH v3 0/9] backlight: qcom-wled: fix and solidify handling of enabled-strings Message-ID: References: <20211115203459.1634079-1-marijn.suijten@somainline.org> <20211116120213.n7qxqfi62lrxhyl7@maple.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20211116120213.n7qxqfi62lrxhyl7@maple.lan> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 16 Nov 2021, Daniel Thompson wrote: > Hi Lee > > On Mon, Nov 15, 2021 at 09:34:50PM +0100, Marijn Suijten wrote: > > This patchset fixes WLED's handling of enabled-strings: besides some > > cleanup it is now actually possible to specify a non-contiguous array of > > enabled strings (not necessarily starting at zero) and the values from > > DT are now validated to prevent possible unexpected out-of-bounds > > register and array element accesses. > > Off-by-one mistakes in the maximum number of strings, also causing > > out-of-bounds access, have been addressed as well. > > They have arrived piecemeal (during v1, v2 and v3) but all patches on > the set should now have my R-b: attached to them. I can see that. Nothing for you to worry about. I'll apply these when I conduct my next sweep, thanks. -- Lee Jones [李琼斯] Senior Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog