From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fd01.gateway.ufhost.com (fd01.gateway.ufhost.com [61.152.239.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 278AD42388; Mon, 18 Dec 2023 15:38:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=starfivetech.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=starfivetech.com Received: from EXMBX165.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX165", Issuer "EXMBX165" (not verified)) by fd01.gateway.ufhost.com (Postfix) with ESMTP id C7E607FD6; Mon, 18 Dec 2023 23:37:56 +0800 (CST) Received: from EXMBX072.cuchost.com (172.16.6.82) by EXMBX165.cuchost.com (172.16.6.75) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Mon, 18 Dec 2023 23:37:56 +0800 Received: from localhost.localdomain (202.188.176.82) by EXMBX072.cuchost.com (172.16.6.82) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Mon, 18 Dec 2023 23:37:50 +0800 From: Ji Sheng Teoh To: CC: , , , , , , , , , , , Subject: Re: [PATCH v4 1/1] dt-bindings: watchdog: starfive,jh7100-wdt: Add compatible for JH8100 Date: Mon, 18 Dec 2023 23:37:38 +0800 Message-ID: <20231218153738.1054393-1-jisheng.teoh@starfivetech.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <1d7f9cbe-9ca1-4ccb-b90f-6e474c0740ad@linaro.org> References: <1d7f9cbe-9ca1-4ccb-b90f-6e474c0740ad@linaro.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-ClientProxiedBy: EXCAS062.cuchost.com (172.16.6.22) To EXMBX072.cuchost.com (172.16.6.82) X-YovoleRuleAgent: yovoleflag Content-Transfer-Encoding: quoted-printable On Mon, 18 Dec 2023 15:41:37 +0100 Krzysztof Kozlowski wrote: > On 18/12/2023 15:27, Ji Sheng Teoh wrote: > >> > >> I have real doubts that you ever tested your entire solution with > >> this binding. Where is the DTS? > >> =20 > >=20 > > Currently, the DTS is still in internal and yet to upstream as it > > depends on [1]. =20 >=20 > Yeah, so you send untested code which cannot work or pass tests. If > you do not test your code, we need to be able to at least verify it, > so send your DTS. Otherwise I cannot trust that this works at all. > Will submit it with DTS once things have cleared up. Thanks for the comment.=20 > Best regards, > Krzysztof >=20