From: Philip Li <philip.li@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency'
Date: Tue, 14 Feb 2017 10:07:29 +0800 [thread overview]
Message-ID: <20170214020729.GB10346@intel.com> (raw)
In-Reply-To: <20170213035759.GH8498@vireshk-i7>
On Mon, Feb 13, 2017 at 09:27:59AM +0530, Viresh Kumar wrote:
> On 13-02-17, 11:41, Philip Li wrote:
> > on the other side, this is a build issue from randconfig, looks the failure exists on linus/master
> > head 1ce4284, and caused by 655c9df commit. Not sure whether you can reproduce it, or if it is not
> > a real issue, we can further follow up to fix false warning.
>
> I don't think so. This is what your report says:
>
> reproduce:
> git checkout 655c9df961751ce21466f6e97e8033932c27a675
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> It never said that you can checkout 1ce4284 and reproduce this.
>
> Can you try to reproduce it on 1ce4284? I am sure you wouldn't find anything.
ah, it looks like a false reporting, both commits are ok.
I will follow up to fix this. sorry for inconvenience caused.
>
> --
> viresh
prev parent reply other threads:[~2017-02-14 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 19:35 drivers/base/power/opp/core.c:241:15: error: redefinition of 'dev_pm_opp_get_max_volt_latency' kbuild test robot
2017-02-13 3:13 ` Viresh Kumar
2017-02-13 3:35 ` Philip Li
2017-02-13 3:34 ` Viresh Kumar
2017-02-13 3:41 ` Philip Li
2017-02-13 3:57 ` Viresh Kumar
2017-02-14 2:07 ` Philip Li [this message]
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=20170214020729.GB10346@intel.com \
--to=philip.li@intel.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=viresh.kumar@linaro.org \
/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.