From: Jens Axboe <axboe@kernel.dk>
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 187/302] mm/page_io.c:405:18: error: 'REQ_HIPRI' undeclared; did you mean 'RWF_HIPRI'?
Date: Fri, 14 Dec 2018 21:29:59 -0700 [thread overview]
Message-ID: <4553850c-9084-7209-eecf-36abc77a58ea@kernel.dk> (raw)
In-Reply-To: <201812150739.LplJThib%fengguang.wu@intel.com>
On 12/14/18 4:04 PM, kbuild test robot wrote:
> tree: git://git.cmpxchg.org/linux-mmotm.git master
> head: 6d5b029d523e959579667282e713106a29c193d2
> commit: 80509a64e354a3de67cfe4dee1cf51c8a2512e44 [187/302] mm/page_io.c: fix polled swap page in
> config: x86_64-rhel-7.2-clear (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> git checkout 80509a64e354a3de67cfe4dee1cf51c8a2512e44
> # 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 errors (new ones prefixed by >>):
>
> mm/page_io.c: In function 'swap_readpage':
>>> mm/page_io.c:405:18: error: 'REQ_HIPRI' undeclared (first use in this function); did you mean 'RWF_HIPRI'?
> bio->bi_opf |= REQ_HIPRI;
> ^~~~~~~~~
> RWF_HIPRI
> mm/page_io.c:405:18: note: each undeclared identifier is reported only once for each function it appears in
The patch just needs to be ordered after the block tree in -mm, then
there are no concerns.
--
Jens Axboe
prev parent reply other threads:[~2018-12-15 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 23:04 kbuild test robot
2018-12-15 4:29 ` Jens Axboe [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=4553850c-9084-7209-eecf-36abc77a58ea@kernel.dk \
--to=axboe@kernel.dk \
--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