From: Rong Chen <rong.a.chen@intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
kbuild test robot <lkp@intel.com>
Cc: Clark Williams <williams@redhat.com>,
linux-rt-users@vger.kernel.org, kbuild-all@01.org,
linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] [PATCH RT] rt: convert mm/kasan/quarantine_lock to raw_spinlock
Date: Thu, 18 Oct 2018 17:04:01 +0800 [thread overview]
Message-ID: <83c8a7a7-00be-b29b-fa2e-be9c8276be94@intel.com> (raw)
In-Reply-To: <20181005163754.2eexrmhzvdltswdr@linutronix.de>
On 10/06/2018 12:37 AM, Sebastian Andrzej Siewior wrote:
> On 2018-09-19 04:34:50 [+0800], kbuild test robot wrote:
>> Hi Clark,
>>
>> Thank you for the patch! Perhaps something to improve:
>>
>> [auto build test WARNING on linux-rt-devel/for-kbuild-bot/current-stable]
>>
>> url: https://github.com/0day-ci/linux/commits/Clark-Williams/rt-convert-mm-kasan-quarantine_lock-to-raw_spinlock/20180919-021343
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git for-kbuild-bot/current-stable
>> config: x86_64-allmodconfig (attached as .config)
>> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
>> reproduce:
>> # save the attached .config to linux build tree
>> make ARCH=x86_64
>>
>> All warnings (new ones prefixed by >>):
> how is this related? Could someone please explain this.
>
>
It Iooks like a kbuild issue, we will looking into it.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2018-10-18 9:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 15:29 [PATCH RT] rt: convert mm/kasan/quarantine_lock to raw_spinlock Clark Williams
2018-09-18 20:34 ` kbuild test robot
2018-10-05 16:37 ` Sebastian Andrzej Siewior
2018-10-18 9:04 ` Rong Chen [this message]
2018-10-05 16:30 ` [PATCH] kasan: convert kasan/quarantine_lock " Sebastian Andrzej Siewior
2018-10-05 16:33 ` Sebastian Andrzej Siewior
2018-10-08 0:47 ` Clark Williams
2018-10-08 9:15 ` Dmitry Vyukov
2018-10-09 14:27 ` Sebastian Andrzej Siewior
2018-10-10 8:25 ` Dmitry Vyukov
2018-10-10 9:29 ` Sebastian Andrzej Siewior
2018-10-10 9:45 ` Dmitry Vyukov
2018-10-10 9:53 ` Sebastian Andrzej Siewior
2018-10-10 9:57 ` Dmitry Vyukov
2018-10-10 21:49 ` [PATCH] mm/kasan: make quarantine_lock a raw_spinlock_t Sebastian Andrzej Siewior
2018-10-11 8:03 ` Dmitry Vyukov
2018-10-12 23:56 ` Andrew Morton
2018-10-13 13:50 ` Peter Zijlstra
2018-10-15 23:35 ` Andrew Morton
2018-10-19 10:58 ` Peter Zijlstra
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=83c8a7a7-00be-b29b-fa2e-be9c8276be94@intel.com \
--to=rong.a.chen@intel.com \
--cc=bigeasy@linutronix.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=williams@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).