From: kbuild test robot <lkp@intel.com>
To: Jan Kara <jack@suse.com>
Cc: kbuild-all@01.org, axboe@kernel.dk,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.com>
Subject: Re: [PATCH] block: Don't allow illegal discard requests
Date: Wed, 4 Nov 2015 18:48:18 +0800 [thread overview]
Message-ID: <201511041829.c5iK0i0O%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446628721-11030-1-git-send-email-jack@suse.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Hi Jan,
[auto build test ERROR on: ext3/for_next]
[cannot apply to: v4.3 next-20151103]
url: https://github.com/0day-ci/linux/commits/Jan-Kara/block-Don-t-allow-illegal-discard-requests/20151104-172203
base: https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_next
config: avr32-atngw100_defconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=avr32
All errors (new ones prefixed by >>):
block/built-in.o: In function `ll_back_merge_fn':
>> (.text+0x90dc): undefined reference to `__avr32_umod64'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 11783 bytes --]
next prev parent reply other threads:[~2015-11-04 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 9:18 [PATCH] block: Don't allow illegal discard requests Jan Kara
2015-11-04 10:46 ` kbuild test robot
2015-11-04 10:48 ` kbuild test robot [this message]
2015-11-04 10:53 ` kbuild test robot
2015-11-04 11:30 ` Christoph Hellwig
2015-11-04 14:17 ` Jan Kara
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=201511041829.c5iK0i0O%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=jack@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.