From: Viresh Kumar <viresh.kumar@linaro.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: drivers/base/power/opp/of.c:181:6: error: redefinition of 'dev_pm_opp_of_remove_table'
Date: Fri, 28 Oct 2016 10:35:46 +0530 [thread overview]
Message-ID: <20161028050546.GK10423@vireshk-i7> (raw)
In-Reply-To: <20161028040752.feghwdavaachpon6@wfg-t540p.sh.intel.com>
On 28-10-16, 12:07, Fengguang Wu wrote:
> On Fri, Oct 28, 2016 at 09:27:53AM +0530, Viresh Kumar wrote:
> >On 28-10-16, 07:22, kbuild test robot wrote:
> >>tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> >>head: e3300ffef0653774f1099cab153d25d24bd773ce
> >>commit: f47b72a15a9679dd4dc1af681d4d2f1ca2815552 PM / OPP: Move CONFIG_OF dependent code in a separate file
> >>date: 6 months ago
> >
> >Why are we picking it up now ?
>
> Sorry due to problems in the 0day infrastructure some few errors are
> missed in May. Now we catch it when the commit goes mainline.
>
> https://lists.01.org/pipermail/kbuild-all/
>
> June 2016: ... [ Gzip'd Text 853 KB ]
> May 2016: ... [ Gzip'd Text 294 KB ]
> April 2016: ... [ Gzip'd Text 599 KB ]
>
> As you can see, the report volumes are noticeably lower in "May 2016".
No issues :)
So I will just ignore this email now as things are probably stable
right now.
--
viresh
next prev parent reply other threads:[~2016-10-28 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 23:22 kbuild test robot
2016-10-28 3:57 ` Viresh Kumar
2016-10-28 4:07 ` Fengguang Wu
2016-10-28 5:05 ` Viresh Kumar [this message]
2017-02-12 21:43 kbuild test robot
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=20161028050546.GK10423@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®