Received: by 10.223.185.116 with SMTP id b49csp714733wrg; Sat, 10 Feb 2018 17:53:52 -0800 (PST) X-Google-Smtp-Source: AH8x224MZA7ggqEnvKwPFeWy62d6Te24cN12aWrqTQbpjmjQ8ROA9SGxy9pcKEZ2sbs6nCWM92iz X-Received: by 2002:a17:902:7b85:: with SMTP id w5-v6mr6756196pll.195.1518314032087; Sat, 10 Feb 2018 17:53:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518314032; cv=none; d=google.com; s=arc-20160816; b=WzZzmDhucyHzt4iIaid0WViK6T381yQkxRoMM/wNToVRpoZwz9MtoXYumlWBsiiTgF DC9lNe+WIYF9HaUbYIv2Rt4R7ES9tlnV1Yi5q0dlLk7DvNo3zFVOVLvMdrK79y57y6Fj tC9M02Ag9ltEBPfu7Ri05mtMWNeNcwzTFlsTn4AHV5+s8hOVe4xZ4viZAdvdv+XLhY00 6HG6NaagSIwl0nfDvizuK7+uMwBeJGQpMHBiEFbdbE8+NjD6UMQO5YUx/wyhdjeFBv1x L/YPeYsi4pJaHsVb3RPjuM9wUuy5nG3093tdd7TCruURsBNV9coYspJNLOJi+6K22UAH W9ZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=g96i2ppdN/vR2OqgO08cun1hCG3D5FFE7qpPouNLPLM=; b=NLzG5DayCUcwx59vNBt5k77ZFb8+Ks0NzSZYeMlPBFRlqj6m/nojIDx1Kd1GagZhGD x+LioecXineznEjwocgYolRzO1p+D/j9jyDQHHIuE302h8j4e1mUjBtqJi2W2YwLS5vd CGQpYMN1Gp/kJ2Qh7ldK9ADL2GSgJJpUiin9lICWFYP8vPVSfB/NmfmDUXZq3+VjEnyh LEbtSMNMmYcsDjD3So2H/5ioqa0Cpz82I9/04hguDjIqLUVAgC9tkfyYkJV03AgXjo3t 8LcN9wiONNl7lKnw44Ff32UsTdy61/qehu7IRjEsGg1a+Oskh+D9vWZ3cuxVn97EL1th iVBg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=koPGlvGs; 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 t25si3399451pgo.398.2018.02.10.17.53.36; Sat, 10 Feb 2018 17:53:52 -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; dkim=fail header.i=@gmail.com header.s=20161025 header.b=koPGlvGs; 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 S1751317AbeBKBw4 (ORCPT + 99 others); Sat, 10 Feb 2018 20:52:56 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:40158 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751050AbeBKBwy (ORCPT ); Sat, 10 Feb 2018 20:52:54 -0500 Received: by mail-pg0-f68.google.com with SMTP id g2so5549587pgn.7; Sat, 10 Feb 2018 17:52:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=g96i2ppdN/vR2OqgO08cun1hCG3D5FFE7qpPouNLPLM=; b=koPGlvGsM5FvbMrKSHMSiBRUSHs0DsBAQOdEuHzC9CQB5MQHjzW0S4wUeFDaE9qfyl /4j17DV7CLGctIUP9hsj2RQ1ANbtDRaMYt4VGzz8hpSdkn8UHhfjASGD1omx3xWF3Zii LTbxvXsYl1Dol5FYMswZsrDHehGgt+rEEhn4HO8w0aF2YDWrikchZCcCgZnZ62gS1vj5 GDUN4n9ADx+y7LvnbDo6C04OG9fuvfUR6A2QWWGX9nwqZpeHIH5myT8pHgATsw4lgo1W oxbibOkvs+t4s9RIx/S2VfsenQ8IQedEs9o024fUlrNzzdCR/zUp8PQ2c6YZM5wWsnNQ jF5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=g96i2ppdN/vR2OqgO08cun1hCG3D5FFE7qpPouNLPLM=; b=Kt58sa9uO+xNLyk3ScWCR6Vtb3mWKVeRErYSnJNJk6ZJq3J5/ksPV1fpUhVrbPsK/D HErN/mXkODOyo9tcfBuoyDah1ZtILY2AwG6TTSf6CkOMPKCk68iCDbNWjw9g9Lys2+9w /bJV6PF4czTzRnoHS7u/XljfDfJC8vlv4RyYLEOVizuEAnSTAvIRgHunfX4ya2EUM+/i p8w3XPJ0Cr5fnvYSLxHrd/PdRgchUcgGe5X9FdOy5g/l5QS/wwYNkMX/m2XtiOmbYBqD BuJeJdxcFfLw7WUz01+NEgN7wcu1iUY95OcngMbgvcBcvwRF2JOLPBnSNqklceorl19j Psdg== X-Gm-Message-State: APf1xPAJIcZVMQQx6yHatLw8fNiRcl30+1vEqOXeomVpEpMankyVPH+D eUTS773Yg4NBWJjX6rS+MEA= X-Received: by 10.99.115.92 with SMTP id d28mr5906091pgn.359.1518313973283; Sat, 10 Feb 2018 17:52:53 -0800 (PST) Received: from server.roeck-us.net (108-223-40-66.lightspeed.sntcca.sbcglobal.net. [108.223.40.66]) by smtp.gmail.com with ESMTPSA id b88sm7406102pfd.108.2018.02.10.17.52.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Feb 2018 17:52:52 -0800 (PST) Subject: Re: [PATCH v2 5/7] watchdog: mtk: allow setting timeout in devicetree To: Marcus Folkesson , Sean Wang 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 , devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org 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> From: Guenter Roeck Message-ID: <5449674d-2812-c9b5-9c06-af2fbfa72737@roeck-us.net> Date: Sat, 10 Feb 2018 17:52:49 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180210201207.GC744@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks, Guenter