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 5066DC41513 for ; Sun, 6 Aug 2023 17:53:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229509AbjHFRxo (ORCPT ); Sun, 6 Aug 2023 13:53:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50706 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229581AbjHFRxn (ORCPT ); Sun, 6 Aug 2023 13:53:43 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 24CAA1716; Sun, 6 Aug 2023 10:53:42 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 9118D6121D; Sun, 6 Aug 2023 17:53:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5CE5BC433C7; Sun, 6 Aug 2023 17:53:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1691344421; bh=TiEcOPbSzVD11ZN5C0JGXcIfrthE91VTmMn1kJ2hHw8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=PLYFUhc4c2EfIWmheHVngM7CkBbPeNKza7QyeGlk8VaDRUZSqt3uEDlcZgFcEq/nA caNltPlf76c6Gt5SorNokpC60hbI3TysPqPcA8ACp+YjygEGwlyAhm0WeOjqljiIHy 8wEYdbet8HkYehfMjTJVU4y5E+e/WHbxgmBFdaOHXc8SIzFK2qu98D22WERhFWEdyK dgkoi5QkYG38JrfdW5aLlJNEwnByYpW8Ujwi7KVB4MZtCuKEALPvlxuEXCx6iPtDiT L4rRKrRMHP6oJOe8P+r4oVKtlDkr6fDSEefoo0/jDkYs4XuLG6ZLuaag/LA+rDNsus kAbg6awR19i2A== Message-ID: <5b4bd1cd-ff2d-3aef-8e14-ec3b3c158864@kernel.org> Date: Sun, 6 Aug 2023 12:53:38 -0500 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 v3 3/5] dt-bindings: clock: add Intel Agilex5 clock manager Content-Language: en-US To: "Rabara, Niravkumar L" , Conor Dooley Cc: "Ng, Adrian Ho Yin" , "andrew@lunn.ch" , "conor+dt@kernel.org" , "devicetree@vger.kernel.org" , "krzysztof.kozlowski+dt@linaro.org" , "linux-clk@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "Turquette, Mike" , "netdev@vger.kernel.org" , "p.zabel@pengutronix.de" , "richardcochran@gmail.com" , "robh+dt@kernel.org" , "sboyd@kernel.org" , "wen.ping.teh@intel.com" References: <20230801010234.792557-4-niravkumar.l.rabara@intel.com> <20230802025842.1260345-1-niravkumar.l.rabara@intel.com> <20230802-reuse-diffusion-d41ed8175390@wendy> From: Dinh Nguyen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 8/2/23 02:14, Rabara, Niravkumar L wrote: > > >> -----Original Message----- >> From: Conor Dooley >> Sent: Wednesday, 2 August, 2023 3:02 PM >> To: Rabara, Niravkumar L >> Cc: Ng, Adrian Ho Yin ; andrew@lunn.ch; >> conor+dt@kernel.org; devicetree@vger.kernel.org; dinguyen@kernel.org; >> krzysztof.kozlowski+dt@linaro.org; linux-clk@vger.kernel.org; linux- >> kernel@vger.kernel.org; Turquette, Mike ; >> netdev@vger.kernel.org; p.zabel@pengutronix.de; >> richardcochran@gmail.com; robh+dt@kernel.org; sboyd@kernel.org; >> wen.ping.teh@intel.com >> Subject: Re: [PATCH v3 3/5] dt-bindings: clock: add Intel Agilex5 clock >> manager >> >> On Wed, Aug 02, 2023 at 10:58:42AM +0800, niravkumar.l.rabara@intel.com >> wrote: >>> From: Niravkumar L Rabara >>> >>> Add clock ID definitions for Intel Agilex5 SoCFPGA. >>> The registers in Agilex5 handling the clock is named as clock manager. >>> >>> Signed-off-by: Teh Wen Ping >>> Reviewed-by: Dinh Nguyen >>> Reviewed-by: Conor Dooley >>> Signed-off-by: Niravkumar L Rabara >> >> Damn, I was too late - you already sent a v3 :/ >> >> However, there only seems to be a v3 of this one patch and it was sent in >> reply to the v2 series? The normal thing to do is resend the entire series, not >> just one patch, as a new thread. Not using a new thread may make it harder >> to apply & will also bury the email in people's mailboxes that use things like >> mutt. A single patch as a reply is also confusing, as the rest of the v3 looks like >> it is missing! >> >> Thanks, >> Conor. > > Sorry I made a mistake. > Should I send out entire series with PATCH v3 subject? Or should I wait for review comment on remaining patches and then send entire series with rework and subject prefix PATCH v3? > No need to send out a V3. I've applied patches 1-3 and 5. Will give a little more time for the clk patch. Dinh