From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-f65.google.com ([209.85.161.65]:38285 "EHLO mail-yw1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728042AbgAUDU6 (ORCPT ); Mon, 20 Jan 2020 22:20:58 -0500 Subject: Re: [RFC PATCH 0/3] Add device tree build information 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> From: Frank Rowand Message-ID: Date: Mon, 20 Jan 2020 21:20:55 -0600 MIME-Version: 1.0 In-Reply-To: <20200120182837.GO3697@linaro.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: 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 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? -Frank