From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fhigh-a4-smtp.messagingengine.com (fhigh-a4-smtp.messagingengine.com [103.168.172.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BA76734028D for ; Wed, 18 Mar 2026 12:58:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=103.168.172.155 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773838730; cv=none; b=DN9DU7Yo+6Hz+696pn40d6yVz/IVRqhifU4pUFY5vKroX2jRZmIzKNZvQJXDALgaVe4MzKWsUjFy/lfyRYgc1FtPFb75ntNQOy+zWHJScjcEPc3HXLD7aqyiy2uhzUN9lvSIFaZihKKwMHI5Rp3tywRkC3JObPhlXVgMYlcz7ww= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773838730; c=relaxed/simple; bh=C5Cbap8oIXjaj9N/uWKLtgE6N2nyzeH7FvCbifYxsH4=; h=MIME-Version:Date:From:To:Cc:Message-Id:In-Reply-To:References: Subject:Content-Type; b=hwlLNaZ+mv0JiowhlRSD3z+J5prOhchwFzZTzsa2EXta2P6mHeCoSY9B59u61ts5DSa90DqccTIZRmXy0AzQqVOHoY6VTPgBoObPJpdG7jesM0viNmM8lgPqy063C7esHptddMUXT8ghpZa+29jt4aJDphG6EYpgJemR3xWsjUg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arndb.de; spf=pass smtp.mailfrom=arndb.de; dkim=pass (2048-bit key) header.d=arndb.de header.i=@arndb.de header.b=LJwZ8qoC; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=Yf/NjsNa; arc=none smtp.client-ip=103.168.172.155 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arndb.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arndb.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=arndb.de header.i=@arndb.de header.b="LJwZ8qoC"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="Yf/NjsNa" Received: from phl-compute-04.internal (phl-compute-04.internal [10.202.2.44]) by mailfhigh.phl.internal (Postfix) with ESMTP id 1FD991400243; Wed, 18 Mar 2026 08:58:49 -0400 (EDT) Received: from phl-imap-02 ([10.202.2.81]) by phl-compute-04.internal (MEProxy); Wed, 18 Mar 2026 08:58:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arndb.de; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1773838729; x=1773925129; bh=NgETNFSkBCuNe00TK+uyXLmxYSvaHFnqr/AOivVYrGg=; b= LJwZ8qoCOvpuw2sP0qvk6qXRdGJm52uroDrWcWj7BIimYw2bPdiuK5N+0jxStovX aOE4g+Iy9XRLS0uMe8kabVvquTlfpuk7LZ5fVZwpNyDStOoSUw5xxecS9WXhYBHq he+HcMKx4o/dgAl3L0BAfuKtbqG68IPSfecPvAM80Ie7lYbcT2sdHl/6MLdQj2b4 2Mk20B0gk4uF8BCKaO/7aZ885/JjL1fHHIS9wEIAgHHFVi/RSbvi48Z1MXKKArbg HhX0vFK6VRywaa55DlT/bwDqn8GnUvnIsnodwVU3TfHo0IGGqZo4jgq7FvL+HA3R 7REeqKkpQzJNddlcL7wesw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1773838729; x= 1773925129; bh=NgETNFSkBCuNe00TK+uyXLmxYSvaHFnqr/AOivVYrGg=; b=Y f/NjsNafW+O29jaEeA7kJMfCR6QX8OeS39U5TjT6gw0EyzxxPvzBTcP3dc2aQ4YL JD1uHbTury0m6rQ3VProognDyz4X7+4f0LOaADcL2wAb8gSjEcOFSr4cA2eXs2MD aLj4NzFBxIaS+TUNOmNCuIbw1jdBpetXbVcm30JrDV6y3JO6ijiTxkJ8FL4zmOh0 6BT8sMNSufEqGmY1a+ifG6wOmkIO0TwZtApU6QY9IE0HLjQTn6a/VCqRM5io1d5+ eF2gEsMk7cEYZ+cdThF8yvwQ1oWlm1X26wC3+WvbpYPUNS8HW+J99XMqYbJdYxqf J/F1hy2yM+H6TlErV0Zfw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdeftdegudelucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepofggfffhvfevkfgjfhfutgfgsehtjeertdertddtnecuhfhrohhmpedftehrnhgu uceuvghrghhmrghnnhdfuceorghrnhgusegrrhhnuggsrdguvgeqnecuggftrfgrthhtvg hrnhephfdthfdvtdefhedukeetgefggffhjeeggeetfefggfevudegudevledvkefhvdei necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghrnh gusegrrhhnuggsrdguvgdpnhgspghrtghpthhtohepiedpmhhouggvpehsmhhtphhouhht pdhrtghpthhtohepmhgrghhnuhhsrdgurghmmhesghhmrghilhdrtghomhdprhgtphhtth hopehkrhiikheskhgvrhhnvghlrdhorhhgpdhrtghpthhtohepghgvvghrtheslhhinhhu gidqmheikehkrdhorhhgpdhrtghpthhtoheplhhinhhugidqrghrmhdqkhgvrhhnvghlse hlihhsthhsrdhinhhfrhgruggvrggurdhorhhgpdhrtghpthhtohepshhotgeslhhishht shdrlhhinhhugidruggvvhdprhgtphhtthhopehlihhnuhigqdhrvghnvghsrghsqdhsoh gtsehvghgvrhdrkhgvrhhnvghlrdhorhhg X-ME-Proxy: Feedback-ID: i56a14606:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id D40AA700069; Wed, 18 Mar 2026 08:58:48 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface Precedence: bulk X-Mailing-List: soc@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-ThreadId: AXMg69VYQg4R Date: Wed, 18 Mar 2026 13:58:28 +0100 From: "Arnd Bergmann" To: "Krzysztof Kozlowski" , "Geert Uytterhoeven" Cc: soc@lists.linux.dev, "Magnus Damm" , linux-arm-kernel@lists.infradead.org, Linux-Renesas Message-Id: In-Reply-To: <69927bd8-d476-4a24-91af-f21cdc0bce80@kernel.org> References: <20260314-quick-gray-saluki-0f96ff@quoll> <69927bd8-d476-4a24-91af-f21cdc0bce80@kernel.org> Subject: Re: [GIT PULL 3/4] Renesas DT binding updates for v7.1 Content-Type: text/plain Content-Transfer-Encoding: 7bit On Tue, Mar 17, 2026, at 10:53, Krzysztof Kozlowski wrote: > On 17/03/2026 10:29, Krzysztof Kozlowski wrote: >>>> See also submitting patches in DT dir. >>> >>> So the second commit is subject to II.3: >>> >>> 3) For a series going through multiple trees, the binding patch should be >>> kept with the driver using the binding. >>> >>> In this particular case, I could have included it in my drivers branch. >>> Where do I put SoC-specific DT binding changes that are not picked >>> up by anyone else (I don't have any this time)? >> >> What is "SoC-specific"? You put the DT binding with the user, that was >> always the rule and that is implied by submitting patches. If you do not >> have any user, why would you pick that up? > > Actually I want to correct myself or explain more. If you document ABI > for existing driver with DTS user of the ABI, but without driver change, > e.g. new front compatible when using already documented fallback, I > would keep the change in the driver branch, even though technically the > DTS is the user of new compatible. That is what I was always doing at least. > > Why? Because I expect there might be a next patchset with binding+driver > adding new fallback to the same binding, which would have to go via > driver branch because of mentioned submitting patches rule. Therefore if > I put that first binding in DTS branch and in the future I want to put > next change in the driver branch I would have unnecessary conflicts. Right, this makes sense, though I've been rather relaxed about binding updates in the past, merging them either through the soc/drivers branches if they came with the driver changes, or through the soc/dt branch otherwise. Arnd