cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [gfs2:page_mkwrite-off-by-one 2/7] buffer.c:undefined reference to `page_mkwrite_check_truncate'
Date: Fri, 14 Feb 2020 05:51:39 +0800	[thread overview]
Message-ID: <202002140533.zi0XPul4%lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git page_mkwrite-off-by-one
head:   63e24dff38ac137273e65ebc7929bcaa4bdcd6fe
commit: c6cdee25b520cc250b8dc55b1032c46aa80ca514 [2/7] fs: Switch to page_mkwrite_check_truncate in block_page_mkwrite
config: m68k-m5307c3_defconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout c6cdee25b520cc250b8dc55b1032c46aa80ca514
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=m68k 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   fs/buffer.o: In function `block_page_mkwrite':
>> buffer.c:(.text+0x3c14): undefined reference to `page_mkwrite_check_truncate'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all at lists.01.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 8714 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20200214/db38ed93/attachment.gz>

                 reply	other threads:[~2020-02-13 21:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202002140533.zi0XPul4%lkp@intel.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).