From: Davidlohr Bueso <dave@stgolabs.net>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mmotm:master 291/302] fs/buffer.c:2400:37: error: expected statement before ')' token
Date: Sat, 15 Dec 2018 11:23:46 -0800 [thread overview]
Message-ID: <20181215192346.z6hitrgdsfng76ik@linux-r8p5> (raw)
In-Reply-To: <201812151636.P1KU0v8x%fengguang.wu@intel.com>
On Sat, 15 Dec 2018, kbuild test robot wrote:
>tree: git://git.cmpxchg.org/linux-mmotm.git master
>head: 6d5b029d523e959579667282e713106a29c193d2
>commit: dc946e7f683be2016c12d8d75e6dd3a28a0d3adb [291/302] fs/: remove caller signal_pending branch predictions
>config: x86_64-rhel-7.2-clear (attached as .config)
>compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
>reproduce:
> git checkout dc946e7f683be2016c12d8d75e6dd3a28a0d3adb
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
>Note: the mmotm/master HEAD 6d5b029d523e959579667282e713106a29c193d2 builds fine.
> It only hurts bisectibility.
>
>All error/warnings (new ones prefixed by >>):
>
> fs/buffer.c: In function 'cont_expand_zero':
>>> fs/buffer.c:2400:37: error: expected statement before ')' token
> if (fatal_signal_pending(current))) {
This was fixed by Andrew a while ago:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2a95392eaba5fee94cc22ebf2391a507f7a63636
Thanks,
Davidlohr
prev parent reply other threads:[~2018-12-15 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 8:08 kbuild test robot
2018-12-15 19:23 ` Davidlohr Bueso [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=20181215192346.z6hitrgdsfng76ik@linux-r8p5 \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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