Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp4614792pxb; Tue, 25 Jan 2022 14:32:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJznceT4cgsCxu/Vc9V2Q3HVwbxfEx3T+6o3lMegrrpwXyygBj0vh7gi5L9ItvvLLKd5cqm9 X-Received: by 2002:a17:902:8c97:b0:14a:ec66:bbb0 with SMTP id t23-20020a1709028c9700b0014aec66bbb0mr20128350plo.68.1643149947082; Tue, 25 Jan 2022 14:32:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643149947; cv=none; d=google.com; s=arc-20160816; b=nfHM0eeAuWcZNyXSnbcb3uxQpP2nHLBLa+MERLdHHYZokMIcmttFYZ/oa2xwAZGxjd MdCokEFUPLskV6+W9QDCUUYZ9K9HqnkoL25/wwEY3QRlUAyHJwJVSVjEkIdJHKTtys3Y g1NRgi0OKuKg3Oqn9xr/bk0CYZLmn0A2gu67J/VOuIq1N+6UqwyxyoXkMjZkPPRcwX59 0h65cDI0Hnr17L7fvfDq+K/0m88L9PStmmP+CuPdm97Z1a6/vJyL7DEo7WVmGsAJKz+M StwHpBCJu6x9WCgNf3hCCz0OtkRyEx5zwueJ02KHT2rutl0hRHJCEdLCjub9k/MdP3F6 7kDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date; bh=oQPzpQBcOyXHzChRPIETUa5Sz5pDtSWgF2aT6q6JLr8=; b=XzXS7CZi4sgP/QWndp2Cw36O0uowXmSMGFnDk5xp/2+UiWN6ku86gkITCNanKzB9EJ JHfERLj7wTNS9iwcLiMYXOkf02OLFjWoBFpnQsXG/7COUuNVW0SaRX2b9EARwGIrk8KB UDrJH8gAthTnAZhKFM9yeDfX8XjBYgHgmWd5LakEzkrKGc42ksMPwoiwOyIrttRZ5Rq5 H47CW30GQlwb72pcTp14g0wPEJB0X2xBJyBGs/W2q0mw68R8Fpgo+qDpb8A7+FxVU6Az PumL1unai45ODxfBMJaUo8Ux+N+eUaJFH3NFqjL3dU/iRjHY2k5AM9kwvb50jbPJJ4XX XBtA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i5si1331898pjz.179.2022.01.25.14.32.15; Tue, 25 Jan 2022 14:32:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1580860AbiAYOwv (ORCPT + 99 others); Tue, 25 Jan 2022 09:52:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41714 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1580352AbiAYOsW (ORCPT ); Tue, 25 Jan 2022 09:48:22 -0500 X-Greylist: delayed 535 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Tue, 25 Jan 2022 06:48:13 PST Received: from swift.blarg.de (swift.blarg.de [IPv6:2a01:4f8:c17:52a8::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 5CBC0C061401; Tue, 25 Jan 2022 06:48:13 -0800 (PST) Received: by swift.blarg.de (Postfix, from userid 1000) id D0BE040E4E; Tue, 25 Jan 2022 15:39:16 +0100 (CET) Date: Tue, 25 Jan 2022 15:39:16 +0100 From: Max Kellermann To: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Cc: linux-pwm@vger.kernel.org, thierry.reding@gmail.com, lee.jones@linaro.org, linux-kernel@vger.kernel.org, andrey@lebedev.lt, stable@vger.kernel.org Subject: Re: [PATCH 1/3] pwm-sun4i: convert "next_period" to local variable Message-ID: Mail-Followup-To: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , linux-pwm@vger.kernel.org, thierry.reding@gmail.com, lee.jones@linaro.org, linux-kernel@vger.kernel.org, andrey@lebedev.lt, stable@vger.kernel.org References: <20220125123429.3490883-1-max.kellermann@gmail.com> <20220125143158.qbelqvr5mjq33zay@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220125143158.qbelqvr5mjq33zay@pengutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/01/25 15:31, Uwe Kleine-K?nig wrote: > I think I'd drop this. This isn't a fix worth on it's own to be > backported and if this is needed for one of the next patches, the stable > maintainers will notice themselves (and it might be worth to shuffle > this series to make the fixes come first). The first two patches are preparation for the third patch, which fixes the actual bug. Of course, I could have done everything in one patch, but I thought splitting the first two out makes review easier. This way, every step is almost trivial. If you want me to fold the three patches into one, I can do that. But I can't reorder them (or backport only the bug fix to stable). Max