From: Waiman Long <longman@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking/rwsem: Add DEBUG_RWSEMS to look for lock/unlock mismatches
Date: Tue, 27 Mar 2018 09:21:45 -0400 [thread overview]
Message-ID: <0f7f4e7e-7bdd-3069-8808-944cf34d509c@redhat.com> (raw)
In-Reply-To: <201803271947.1UUNOFXk%fengguang.wu@intel.com>
On 03/27/2018 07:24 AM, kbuild test robot wrote:
> Hi Waiman,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on tip/locking/core]
> [also build test ERROR on v4.16-rc7 next-20180326]
> [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/Waiman-Long/locking-rwsem-Add-DEBUG_RWSEMS-to-look-for-lock-unlock-mismatches/20180327-151310
> config: i386-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=i386
>
> All error/warnings (new ones prefixed by >>):
>
> In file included from include/linux/kernel.h:10:0,
> from kernel/locking/rwsem.c:9:
> kernel/locking/rwsem.c: In function 'up_read_non_owner':
>>> kernel/locking/rwsem.c:217:23: error: implicit declaration of function 'RWSEM_WRITER_OWNED'; did you mean 'RWSEM_READER_OWNED'? [-Werror=implicit-function-declaration]
Yes, I noticed that error right after sending out the patch. That is why
I sent out a v2 patch immediately to fix this. Thanks for the
notification anyway.
Cheers,
Longman
prev parent reply other threads:[~2018-03-27 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 19:11 Waiman Long
2018-03-27 11:24 ` kbuild test robot
2018-03-27 13:21 ` Waiman Long [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=0f7f4e7e-7bdd-3069-8808-944cf34d509c@redhat.com \
--to=longman@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 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®