Received: by 10.223.185.116 with SMTP id b49csp910950wrg; Sat, 10 Feb 2018 23:47:28 -0800 (PST) X-Google-Smtp-Source: AH8x227jXP1YcMaVg2GpMyM+6mB3ZctIA5hDcdja59UOFhEnu2MnbdvwxTJi26FRFSD6/SMvtHGA X-Received: by 2002:a17:902:67:: with SMTP id 94-v6mr7428070pla.183.1518335248426; Sat, 10 Feb 2018 23:47:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518335248; cv=none; d=google.com; s=arc-20160816; b=Jfd5+wP6PbdX6K9mZZc1zAC20apL/3kF0MP2ZITpMQhFbmsUJBBt4uL/z+N4+nThg7 K8oV2JPxW24pVlcFBXJ4MhGcnAeQ4fAsti+RAhjgKWS/NFsGnr38fXUyyx3QUi/lQUp5 o5g/T6p+ozUCsWnnpLmDCm4nk72uVJEpH2fixbZsS8l/vyze7kw3z4Mv46Wf691R327l R+SRChfyB50dzX+QPzUV1S7FiYBOpBtBTVR8AoJ4lu5AEMxCfEuejTQPRI730fzQXHGs /wzcIgC2/x11yHicSri/zujqUqW9boRHu6c5L2QdXHouNY8sqFYpZvIVGaR8TY0Ep7gP 0D3w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=tIQ8MFLRWunKRVmjLggTUjEfEIqXgdAgw9/hWDqGWy8=; b=IdKQu2jfMwSrt/u1O14Tyok2SQX3kZNMEki2UshU8+1XndOKZ0zZ2gn+iTlrYPPKz9 ZFotxCSfeGkijoNzSdzfFxQabFo/JE2op0Nbza6rDQcLTjsEWBZUcsCwXqHrUw2xk6Cb htmzL5a0/MF1LPVi+rySOhVZkQT6V05dtM/wpHqiW6OFZZZf2tyrCqwS1s8UeG+xFkaC 9FGfyULGFaAIdh6OUOALLf8qljbgcpOjYA2OeJuwMET55UxBzgWQRJFBpufjSngUENaR 2I10DPr6ibxYanel3+UPVheQAiCX94IIj4HI6BWKGnrc9HjV3N6MRGoNt39yPWgLvVOU WWEg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b59-v6si4168347plc.302.2018.02.10.23.47.12; Sat, 10 Feb 2018 23:47:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752658AbeBKHqf (ORCPT + 99 others); Sun, 11 Feb 2018 02:46:35 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:54767 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752224AbeBKHqd (ORCPT ); Sun, 11 Feb 2018 02:46:33 -0500 X-UUID: b4de4f487d5a4116bf008fc674db19f4-20180211 Received: from mtkexhb02.mediatek.inc [(172.21.101.103)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 471189417; Sun, 11 Feb 2018 15:46:26 +0800 Received: from mtkcas08.mediatek.inc (172.21.101.126) by mtkmbs03n1.mediatek.inc (172.21.101.181) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 11 Feb 2018 15:46:24 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas08.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1210.3 via Frontend Transport; Sun, 11 Feb 2018 15:46:24 +0800 Message-ID: <1518335184.9025.43.camel@mtkswgap22> Subject: Re: [PATCH v2 5/7] watchdog: mtk: allow setting timeout in devicetree From: Sean Wang To: Guenter Roeck , Marcus Folkesson CC: Wim Van Sebroeck , Rob Herring , "Mark Rutland" , Carlo Caione , "Kevin Hilman" , Matthias Brugger , Barry Song , Maxime Ripard , Chen-Yu Tsai , "Linus Walleij" , Vladimir Zapolskiy , Sylvain Lemieux , Nicolas Ferre , Alexandre Belloni , , , , , , Date: Sun, 11 Feb 2018 15:46:24 +0800 In-Reply-To: <5449674d-2812-c9b5-9c06-af2fbfa72737@roeck-us.net> References: <20180210091911.3644-1-marcus.folkesson@gmail.com> <20180210091911.3644-5-marcus.folkesson@gmail.com> <1518261002.9025.36.camel@mtkswgap22> <20180210124328.GB744@gmail.com> <20180210201207.GC744@gmail.com> <5449674d-2812-c9b5-9c06-af2fbfa72737@roeck-us.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2018-02-10 at 17:52 -0800, Guenter Roeck wrote: > On 02/10/2018 12:12 PM, Marcus Folkesson wrote: > > Hello Sean, > > > > On Sat, Feb 10, 2018 at 01:43:28PM +0100, Marcus Folkesson wrote: > >> Hello Sean, > >> > >> On Sat, Feb 10, 2018 at 07:10:02PM +0800, Sean Wang wrote: > >>> > >>> Hi, Marcus > >>> > >>> The changes you made for dt-bindings and driver should be put into > >>> separate patches. > >> > >> I actually thought about it but chose to have it in the same patch because I > >> did not see any direct advantage to separating them. > >> > >> But I can do that. > >> I will come up with a v3 with this change if no one thinks differently. > >> > > > > When looking at the git log, I'm not that convinced it should be > > separate patches. > > > > For example, I found a4f741e3e157c3a5c8aea5f2ea62b692fbf17338 that is > > doing the exact same thing as this patch. > > > > There is plenty of patches that mixes the code change and dt bindings > > updates. > > Could it not be useful to overview both the implementation and > > dt-mapping change in one view? > > > > If you or anyone else still think it should be separated, please let me know and I will > > come up with a v3. > > > > If we were talking about something new, specifically new and unapproved DT bindings, > it should be separate patches. However, that is not the case here. The DT bindings > are well established. Sure, we could be pedantic and request a split into two > patches. However, the only benefit of that would be more work for the maintainers, > ie Wim and myself (including me having to send this e-mail). I don't really see > the point of that. > > I have already sent my Reviewed-by:, and I don't intend to withdraw it. > Hi, both Sorry for that if I caused any inconvenience to you. I didn't really insist on if the patch is needed to split into two, which totally depends on whether dt maintainers like it. The change for dt-binding is usually added as a split patch with dt-bindings as a prefix. This way I thought dt maintainers is not easy to miss those patches and also can give some useful feedback for them. Sean > Thanks, > Guenter >