From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mg.richtek.com (mg.richtek.com [220.130.44.152]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 35AAA3D62; Thu, 28 Dec 2023 07:27:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=richtek.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=richtek.com X-MailGates: (SIP:2,PASS,NONE)(compute_score:DELIVER,40,3) Received: from 192.168.10.46 by mg.richtek.com with MailGates ESMTPS Server V6.0(636801:0:AUTH_RELAY) (envelope-from ) (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256/256); Thu, 28 Dec 2023 15:27:02 +0800 (CST) Received: from ex3.rt.l (192.168.10.46) by ex3.rt.l (192.168.10.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Thu, 28 Dec 2023 15:27:02 +0800 Received: from linuxcarl2.richtek.com (192.168.10.154) by ex3.rt.l (192.168.10.45) with Microsoft SMTP Server id 15.2.1258.27 via Frontend Transport; Thu, 28 Dec 2023 15:27:02 +0800 Date: Thu, 28 Dec 2023 15:27:02 +0800 From: ChiYuan Huang To: Krzysztof Kozlowski CC: Jonathan Cameron , Krzysztof Kozlowski , Conor Dooley , Lars-Peter Clausen , Rob Herring , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , , , Subject: Re: [PATCH 0/2] RTQ6056: Add compatible for the same chip family Message-ID: <20231228072702.GA14434@linuxcarl2.richtek.com> References: Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) On Thu, Dec 28, 2023 at 08:16:40AM +0100, Krzysztof Kozlowski wrote: > On 28/12/2023 04:51, cy_huang@richtek.com wrote: > > From: ChiYuan Huang > > > > *** Resend for the '--thread' config in 'git format-patch'. > > Resending the same after you receive feedback means you entirely bypass > that feedback. Don't do this. Ever. > Got it. I'm just trying to figure out why Jonathan said the thread cannot be found in lore.kernel.org. Eventually I found that's the 'thread' option. When sending v2 patch series, I think I won't forget it in the future. Not inteneded to bypass the whole suggestion or feedback. Sorry for that. > Best regards, > Krzysztof >