From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Steven Rostedt <rostedt@goodmis.org>, kbuild test robot <lkp@intel.com>
Cc: Alexander Potapenko <glider@google.com>, <kbuild-all@01.org>,
<dvyukov@google.com>, <kcc@google.com>, <x86@kernel.org>,
<mingo@redhat.com>, <kasan-dev@googlegroups.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] x86, kasan, ftrace: Put APIC interrupt handlers into .irqentry.text
Date: Wed, 27 Jul 2016 15:52:08 +0300 [thread overview]
Message-ID: <5798AE78.2040907@virtuozzo.com> (raw)
In-Reply-To: <20160727084517.70020553@gandalf.local.home>
On 07/27/2016 03:45 PM, Steven Rostedt wrote:
> On Fri, 15 Jul 2016 17:19:46 +0800
> kbuild test robot <lkp@intel.com> wrote:
>
>> Hi,
>>
>> [auto build test WARNING on tip/x86/core]
>> [also build test WARNING on v4.7-rc7 next-20160714]
>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>>
>> url: https://github.com/0day-ci/linux/commits/Alexander-Potapenko/x86-kasan-ftrace-Put-APIC-interrupt-handlers-into-irqentry-text/20160715-152601
>> config: x86_64-acpi-redef (attached as .config)
>> compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
>> reproduce:
>> # save the attached .config to linux build tree
>> make ARCH=x86_64
>>
>> All warnings (new ones prefixed by >>):
>>
>>>> arch/x86/entry/entry_64.S:674:15: warning: extra tokens at end of #ifdef directive
>> #ifdef defined(CONFIG_FUNCTION_GRAPH_TRACER) || defined(CONFIG_KASAN)
>
> Alexander,
>
> Can you send a v2 with this fixed?
>
He did - http://lkml.kernel.org/g/<1468575763-144889-1-git-send-email-glider@google.com>
next prev parent reply other threads:[~2016-07-27 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 17:04 [PATCH v1] x86, kasan, ftrace: Put APIC interrupt handlers into .irqentry.text Alexander Potapenko
2016-07-15 9:19 ` kbuild test robot
2016-07-27 12:45 ` Steven Rostedt
2016-07-27 12:52 ` Andrey Ryabinin [this message]
2016-07-27 13:01 ` Steven Rostedt
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=5798AE78.2040907@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kbuild-all@01.org \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.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.