From: Fengguang Wu <fengguang.wu@intel.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [powerpc:next 45/53] warning: (PPC_C2K && ..) selects NOT_COHERENT_CACHE which has unmet direct dependencies (4xx || ..)
Date: Tue, 11 Mar 2014 12:54:24 +0800 [thread overview]
Message-ID: <20140311045424.GB12373@localhost> (raw)
In-Reply-To: <531DD0F4.6020000@windriver.com>
On Mon, Mar 10, 2014 at 10:49:24AM -0400, Paul Gortmaker wrote:
> On 14-03-08 03:07 AM, kbuild test robot wrote:
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git next
> > head: c7e64b9ce04aa2e3fad7396d92b5cb92056d16ac
> > commit: 3c8464a9b12bf83807b6e2c896d7e7b633e1cae7 [45/53] powerpc: Delete old PrPMC 280/2800 support
> > config: make ARCH=powerpc c2k_defconfig
> >
> > All warnings:
> >
> > warning: (PPC_C2K && AMIGAONE) selects NOT_COHERENT_CACHE which has unmet direct dependencies (4xx || 8xx || E200 || PPC_MPC512x || GAMECUBE_COMMON)
>
> This _looks_ like a new warning, but it really is not. If you look
> at the tree prior to the above named commit, it generates this:
>
> $ make c2k_defconfig
> warning: (PPC_PRPMC2800 && PPC_C2K && AMIGAONE) selects NOT_COHERENT_CACHE which has unmet direct dependencies (4xx || 8xx || E200 || PPC_MPC512x || GAMECUBE_COMMON)
> warning: (PPC_PRPMC2800 && PPC_C2K && AMIGAONE) selects NOT_COHERENT_CACHE which has unmet direct dependencies (4xx || 8xx || E200 || PPC_MPC512x || GAMECUBE_COMMON)
> #
> # configuration written to .config
>
> So the warning is slightly different in text, but essentially
> the exact same thing that was being warned about before. We've
> just removed one of the possible symbols from existence.
Yes, sorry, the kbuild robot is not smart enough to detect such
slightly changed error/warnings and will treat them as new ones.
> I'm not sure there would ever be a way to teach kbuild robot
> about something as subtle as the above; just one of the false
> positives that we'll have to live with, probably.
It is false positive: "this bug is not introduced by me!"
However if you take a broader view, it's still notifying the possibly
"relevant" people who may know the background about that bug, or whom
to further CC the report. :)
Thanks,
Fengguang
next parent reply other threads:[~2014-03-11 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <531acfa5.YesaRIJhSRvrw4/w%fengguang.wu@intel.com>
[not found] ` <531DD0F4.6020000@windriver.com>
2014-03-11 4:54 ` Fengguang Wu [this message]
2014-03-11 14:32 ` [powerpc:next 45/53] warning: (PPC_C2K && ..) selects NOT_COHERENT_CACHE which has unmet direct dependencies (4xx || ..) Paul Gortmaker
2014-03-11 23:30 ` Fengguang Wu
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=20140311045424.GB12373@localhost \
--to=fengguang.wu@intel.com \
--cc=benh@kernel.crashing.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.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.