From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Huang Rui <ray.huang@amd.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
acme@kernel.org
Subject: Re: linux-next: Tree for Mar 24 (events/amd/power)
Date: Thu, 24 Mar 2016 10:05:03 -0700 [thread overview]
Message-ID: <56F41E3F.8000407@infradead.org> (raw)
In-Reply-To: <20160324130941.5931a051@canb.auug.org.au>
On 03/23/16 19:09, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v4.7 related material to your linux-next included
> trees until after v4.6-rc1 is released.
>
> Changes since 20160323:
>
on i386:
when CONFIG_CPU_SUP_INTEL is not enabled:
In file included from ../include/linux/kobject.h:21:0,
from ../include/linux/module.h:17,
from ../arch/x86/events/amd/power.c:13:
../arch/x86/events/amd/../perf_event.h:660:31: error: 'events_sysfs_show' undeclared here (not in a function)
.attr = __ATTR(_name, 0444, events_sysfs_show, NULL), \
^
../include/linux/sysfs.h:103:10: note: in definition of macro '__ATTR'
.show = _show, \
^
../arch/x86/events/amd/power.c:181:1: note: in expansion of macro 'EVENT_ATTR_STR'
EVENT_ATTR_STR(power-pkg, power_pkg, "event=0x01");
^
../scripts/Makefile.build:291: recipe for target 'arch/x86/events/amd/power.o' failed
--
~Randy
next prev parent reply other threads:[~2016-03-24 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 2:09 linux-next: Tree for Mar 24 Stephen Rothwell
2016-03-24 5:45 ` Stephen Rothwell
2016-03-24 17:05 ` Randy Dunlap [this message]
2016-03-25 2:41 ` linux-next: Tree for Mar 24 (events/amd/power) Huang Rui
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=56F41E3F.8000407@infradead.org \
--to=rdunlap@infradead.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ray.huang@amd.com \
--cc=sfr@canb.auug.org.au \
/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