From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 6 (scsi_debug.c)
Date: Fri, 2 Sep 2016 08:40:47 -0700 [thread overview]
Message-ID: <dfed0e24-0ea1-d364-9a6a-d07e3d55d178@infradead.org> (raw)
In-Reply-To: <CALLJCT0r7FfL=rLARTV9-YB-x10d1w0hYMOO6BC-dv8zGC4VLA@mail.gmail.com>
On 08/23/16 16:22, Masanari Iida wrote:
> This one still exist on linus's tree (as of v4.8-rc3).
>
> CALL scripts/checksyscalls.sh
> CHK kernel/config_data.h
> Building modules, stage 2.
> MODPOST 720 modules
> ERROR: "ip_compute_csum" [drivers/scsi/scsi_debug.ko] undefined!
> scripts/Makefile.modpost:91: recipe for target '__modpost' failed
> make[1]: *** [__modpost] Error 1
> Makefile:1178: recipe for target 'modules' failed
> make: *** [modules] Error 2
>
> Masanari
Hi,
Do you have the kernel .config file that causes this?
I can no longer reproduce it.
What $arch did you build on?
Thanks.
> On Tue, Jun 7, 2016 at 12:10 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 06/05/16 21:20, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20160603:
>>
>> on x86_64:
>>
>> ERROR: "ip_compute_csum" [drivers/scsi/scsi_debug.ko] undefined!
>>
>> CONFIG_GENERIC_CSUM doesn't seem to exist for x86, so lib/checksum.o is not built.
>>
>>
>> --
>> ~Randy
--
~Randy
next prev parent reply other threads:[~2016-09-02 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 4:20 linux-next: Tree for Jun 6 Stephen Rothwell
2016-06-07 3:10 ` linux-next: Tree for Jun 6 (scsi_debug.c) Randy Dunlap
2016-08-23 23:22 ` Masanari Iida
2016-09-02 15:40 ` Randy Dunlap [this message]
2016-06-07 5:11 ` linux-next: Tree for Jun 6 (mm/slub.c) Randy Dunlap
2016-06-07 20:12 ` Andrew Morton
2016-06-07 21:37 ` Randy Dunlap
2016-06-07 23:31 ` Stephen Rothwell
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=dfed0e24-0ea1-d364-9a6a-d07e3d55d178@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=standby24x7@gmail.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).