Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3250745ybl; Mon, 20 Jan 2020 19:40:38 -0800 (PST) X-Google-Smtp-Source: APXvYqyp2FpTJag5OSmXTb8eNMsCLz4Dg0/SwCMc2LqMf47yzIrpIqAnH28Vc66CU6ARTlN7VF4t X-Received: by 2002:aca:1801:: with SMTP id h1mr1561250oih.16.1579578038184; Mon, 20 Jan 2020 19:40:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579578038; cv=none; d=google.com; s=arc-20160816; b=Pvz8PHnUtI4/aTYf6B1bh6UmSImCo2Xtl3xoRL0SOeuhTwMBV/xGSxO7PKXfepkWEI Plo6caDJvX1CPZzx1SXumtZRmgG1yZ5odExr+KnUYjBPx/23Ie0OTjQB7rPRYta7L0vY RLtm8/b1/11IQ2AhfUg0w0H0d+BA5tunEzK7azQAuRTe6kUGyBeG1RiVqKONp846RyZG nj+KIj1VwsHnwlQAehDwnSW9IdaMtLN9M0Q758ey3oS6CUfuVuDnpoMCaX9E2kvMZrH/ 8fDLWOeJztu9H7PhpMMtwBFf8axW4mUu85qDl7JgRrdGi42mWaDBkBZBXFeWgOQD93EI xzTA== 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:references:cc:to:from:subject:dkim-signature; bh=zdgsz84FvwJzIN/En/yZAdV4WDABHd4kiHJoyghAqMA=; b=ROb2HkKW4Ijh5ynxecosI9EhFBcRHJWI7OI51Lmz3RbUIQSv9ih+dkpWJepMy5pNgV rN6F2AyPsQkL8cYULQxuEaCvsnqTLqPweILsjhR6MVztHR3nNNIEO1fQcjxAOxWEutrx Pr8Vk3t4ZMyX4hlr2DGisIQbdXforGpx/ZAA+xftJp+3GTWiCn27ygNFwXHlrDqyKbOo WSUAfU+G4HuENLOLH5S3Qqd+5CI2aWAafMzzUoJ2J0QctrXW35m0wscAAvVM6V7+4yqS hviG00H0ZBOI2SrXsBhUWKmonFQccYR9K20dLwfrJ+DQfzyaOsa2qX8/PMr5hTjmtKvZ kI5g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=E0rGhZJT; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u21si19014601oic.263.2020.01.20.19.40.25; Mon, 20 Jan 2020 19:40:38 -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=pass header.i=@gmail.com header.s=20161025 header.b=E0rGhZJT; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728680AbgAUDjb (ORCPT + 99 others); Mon, 20 Jan 2020 22:39:31 -0500 Received: from mail-qv1-f66.google.com ([209.85.219.66]:40153 "EHLO mail-qv1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726935AbgAUDjb (ORCPT ); Mon, 20 Jan 2020 22:39:31 -0500 Received: by mail-qv1-f66.google.com with SMTP id dp13so809395qvb.7; Mon, 20 Jan 2020 19:39:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=zdgsz84FvwJzIN/En/yZAdV4WDABHd4kiHJoyghAqMA=; b=E0rGhZJTc7LrntC7wA6B/ETc1nRH8YtUrXlz+Pgq0AHx/c9KXbI4UCuv5Cxtxo0IYP 04KOPPEaVLUD4VgkLT2R5TUn4Nn2eXygh/WPH0fIhFtQpmcQ6ZsCtKqAIe2KHUllEpx1 FQIwhUmuUiA3uxr7eQwyevTVy5fDFV3kfx/JuQ+Wj8n7N/8rWv2qupGBqnrsMoa0E0+a G/yYs9DiMOZwZFDdfMnSI6CweIQxxrPl73jZEgg9IYLTR43pgFBTLMwbkBNmBhFsnVOC TKRylTPKHDXRz6Dh2MIhFRj0oBRMsb7edt4B2VYYzsLv2Js69qqDeN2WMzwQXI9ROUN4 jhXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=zdgsz84FvwJzIN/En/yZAdV4WDABHd4kiHJoyghAqMA=; b=TLvabdMefNcSBXnQtp7Pnu8ckGyfVFIfI4xaM5jPg+GzKd++GM4CzeJ0qUOW3puv4W /C5AGtjwE2lGFrXrw6yk7Vw+BVlDu5NW3kdtT4AT7ece63TlysbrMl2S543t/zWUxTg+ bFucE+nxm57pU1ixIPeyL0dBk/f+Gx/Jbt4fviRn6RYN/yehN9xJ/9xFo5tpYyntp3i7 dMEwGzwiYrfuaMoAam0Ng0DiEtGp+HBLc8SOMV42a6YdLn2KxQTB/EYzUTcpYzbu+sXj JQHfF/gby9bX6zgeM5OajQsETO9tRFPsQuinC9vkyLzJJKUwGWiNAF0/zN4dg1CObojr ijvg== X-Gm-Message-State: APjAAAVwFPot1jpsaYv7WFrAy0fbA4iyOt+oM0JouUU0wSffrOQ5Pq7r CXAG4hXhess8w1piY8YvweQ= X-Received: by 2002:ad4:4f45:: with SMTP id eu5mr2948932qvb.235.1579577969907; Mon, 20 Jan 2020 19:39:29 -0800 (PST) Received: from [192.168.1.46] (c-73-88-245-53.hsd1.tn.comcast.net. [73.88.245.53]) by smtp.gmail.com with ESMTPSA id d3sm18165079qtp.25.2020.01.20.19.39.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Jan 2020 19:39:29 -0800 (PST) Subject: Re: [RFC PATCH 0/3] Add device tree build information From: Frank Rowand To: Steve McIntyre Cc: Alexandre Torgue , robh+dt@kernel.org, Masahiro Yamada , Michal Marek , david@gibson.dropbear.id.au, sjg@chromium.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, devicetree-compiler@vger.kernel.org References: <20200113181625.3130-1-alexandre.torgue@st.com> <233e0a5f-d38f-908c-5ca7-66ee87d0fcae@st.com> <7cfd0bc0-13fd-98ea-9bfd-6cfbbfd77b6d@gmail.com> <220e3aea-b273-417a-69c9-059236c888af@st.com> <20200120182837.GO3697@linaro.org> Message-ID: Date: Mon, 20 Jan 2020 21:39:28 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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 1/20/20 9:20 PM, Frank Rowand wrote: > On 1/20/20 12:28 PM, Steve McIntyre wrote: >> Hi Frank! >> >> Thanks for the link back to the previous discussion, it's very >> helpful. >> >> On Mon, Jan 20, 2020 at 10:14:22AM -0600, Frank Rowand wrote: >>> On 1/20/20 4:56 AM, Alexandre Torgue wrote: >> >> ... >> >>>> and the date). There are no "dtb versions", and "absolute/relative" >>>> path which created concerns. One remaining concern is "reproducible >>> >>> Here is an example of the info from one of my builds: >>> >>> From Linux 5.5.0-rc2-dirty by frowand the Mon Jan 20 09:50:58 CST 2020. >>> >>> The information 'Linux 5.5.0-rc2-dirty' is precisely what was most objected >>> to in my proposal. >> >> ACK. :-( I'm surprised to see so much push-back on what looks like a >> simple piece of information here. > > Me too. > > >> >> I've had users *specifically* asking for this kind of identification >> so that they can verify the version of the DTB they're using at >> runtime. Right now it can be a guessing game, which does not help >> people trying to debug problems. >> >> Cheers, >> > > If the information was reported as debug information via pr_debug(), > would that work for your use case? Or would the users' kernels > not have debug enabled in the configuration? And even pr_debug() might not be sufficient since the property value is available via /proc/device-tree if the proc file system is enabled.