From: Jeff Garzik <jeff@garzik.org>
To: Jens Axboe <axboe@suse.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: SCSI make all{yes,mod}config build breakage
Date: Sat, 30 Sep 2006 21:25:40 -0400 [thread overview]
Message-ID: <451F1914.9040007@garzik.org> (raw)
The block tree merge broke the SCSI build:
CC [M] drivers/scsi/libsas/sas_scsi_host.o
In file included from include/scsi/libsas.h:35,
from drivers/scsi/libsas/sas_internal.h:32,
from drivers/scsi/libsas/sas_scsi_host.c:26:
include/scsi/scsi_device.h: In function ‘scsi_device_reprobe’:
include/scsi/scsi_device.h:303: warning: ignoring return value of
‘device_reprobe’, declared with attribute warn_unused_result
drivers/scsi/libsas/sas_scsi_host.c: In function ‘sas_scsi_get_task_attr’:
drivers/scsi/libsas/sas_scsi_host.c:129: error: ‘struct request’ has no
member named ‘flags’
The attached patch (sent in separate email with proper sign-off) fixes
things.
reply other threads:[~2006-10-01 1:25 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=451F1914.9040007@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox