From: Rob Herring <robh@kernel.org>
To: Huang Ying <ying.huang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [lkp] [of] 649e0a77e28:
Date: Mon, 13 Jul 2015 22:31:11 -0500 [thread overview]
Message-ID: <CAL_JsqLRrh_mQCsqv9paZgmYnzMcH=jNnnVQt-Wgr0yJ17sYow@mail.gmail.com> (raw)
In-Reply-To: <1436841447.5489.462.camel@intel.com>
On Mon, Jul 13, 2015 at 9:37 PM, Huang Ying <ying.huang@intel.com> wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 649e0a77e28a7796bf62bfda0fe3f2aee094bd58 ("of: make unittest select OF_EARLY_FLATTREE instead of depend on it")
>
> The following new message in kernel log may make end user confuse.
>
> [ 2.775617] device-tree: Duplicate name in testcase-data, renamed to "duplicate-name#1"
This should probably be after the next line.
> [ 2.779463] ### dt-test ### start of unittest - you will see error messages
Is "you will see error messages" not clear enough?
We could prefix every message to make it clearer. Unit tests often
print error messages and typically should not be enabled on production
kernels.
Rob
> [ 2.780294] /testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
> [ 2.781341] /testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
> [ 2.782394] /testcase-data/phandle-tests/consumer-a: could not find phandle
> [ 2.783001] /testcase-data/phandle-tests/consumer-a: could not find phandle
> [ 2.783622] /testcase-data/phandle-tests/consumer-a: arguments longer than property
> [ 2.784333] /testcase-data/phandle-tests/consumer-a: arguments longer than property
>
>
> Thanks,
> Ying Huang
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: lkp@lists.01.org
Subject: Re: [of] 649e0a77e28:
Date: Mon, 13 Jul 2015 22:31:11 -0500 [thread overview]
Message-ID: <CAL_JsqLRrh_mQCsqv9paZgmYnzMcH=jNnnVQt-Wgr0yJ17sYow@mail.gmail.com> (raw)
In-Reply-To: <1436841447.5489.462.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
On Mon, Jul 13, 2015 at 9:37 PM, Huang Ying <ying.huang@intel.com> wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 649e0a77e28a7796bf62bfda0fe3f2aee094bd58 ("of: make unittest select OF_EARLY_FLATTREE instead of depend on it")
>
> The following new message in kernel log may make end user confuse.
>
> [ 2.775617] device-tree: Duplicate name in testcase-data, renamed to "duplicate-name#1"
This should probably be after the next line.
> [ 2.779463] ### dt-test ### start of unittest - you will see error messages
Is "you will see error messages" not clear enough?
We could prefix every message to make it clearer. Unit tests often
print error messages and typically should not be enabled on production
kernels.
Rob
> [ 2.780294] /testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
> [ 2.781341] /testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
> [ 2.782394] /testcase-data/phandle-tests/consumer-a: could not find phandle
> [ 2.783001] /testcase-data/phandle-tests/consumer-a: could not find phandle
> [ 2.783622] /testcase-data/phandle-tests/consumer-a: arguments longer than property
> [ 2.784333] /testcase-data/phandle-tests/consumer-a: arguments longer than property
>
>
> Thanks,
> Ying Huang
next prev parent reply other threads:[~2015-07-14 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 2:37 [lkp] [of] 649e0a77e28: Huang Ying
2015-07-14 2:37 ` Huang Ying
2015-07-14 3:31 ` Rob Herring [this message]
2015-07-14 3:31 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL_JsqLRrh_mQCsqv9paZgmYnzMcH=jNnnVQt-Wgr0yJ17sYow@mail.gmail.com' \
--to=robh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.