From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] next-20090113 - scsi_debug fails with CONFIG_CRC_T10DIF=n
Date: Tue, 13 Jan 2009 11:51:24 -0600 [thread overview]
Message-ID: <1231869084.4519.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20090113130215.GD2364@linux.vnet.ibm.com>
On Tue, 2009-01-13 at 18:32 +0530, Kamalesh Babulal wrote:
> Hi Stephen,
>
> next-20090113 kernel randconfig fails with
>
> ERROR: "crc_t10dif" [drivers/scsi/scsi_debug.ko] undefined!
> make[1]: *** [__modpost] Error 1
>
> Impact: Fix the dependency of scsi_debug on crc-t10dif library
>
> scsi_debug calls the functions exported by crc-t10dif library,
> adding dependency to select CONFIG_CRC_T10DIF
>
> Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Already spotted by randy:
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=37b1261d045f0b0be09fa1d51efac726385da105
James
next prev parent reply other threads:[~2009-01-13 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 6:51 linux-next: Tree for January 13 Stephen Rothwell
2009-01-13 11:30 ` [BUILD-FAILURE] next-20090113 - powerpc - kernel/idle.c fails at cpu_idle() Kamalesh Babulal
2009-01-13 23:18 ` Stephen Rothwell
2009-01-13 12:03 ` [BUILD-FAILURE] next-20090113 - drivers/scsi/aha1542.c builds with CONFIG_PPC=y Kamalesh Babulal
2009-01-13 17:50 ` James Bottomley
2009-01-13 23:19 ` Stephen Rothwell
2009-01-13 13:02 ` [PATCH] next-20090113 - scsi_debug fails with CONFIG_CRC_T10DIF=n Kamalesh Babulal
2009-01-13 17:51 ` James Bottomley [this message]
2009-01-13 21:31 ` linux-next: Tree for January 13 (gfs2 build error) Randy Dunlap
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=1231869084.4519.22.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).