From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
willy@debian.org,
Linux1394-Devel <linux1394-devel@lists.sourceforge.net>
Subject: Re: [BK PATCH] SCSI updates for 2.6.9
Date: Mon, 18 Oct 2004 23:41:13 -0500 [thread overview]
Message-ID: <200410182341.13648.dtor_core@ameritech.net> (raw)
In-Reply-To: <1098137016.2011.339.camel@mulgrave>
On Monday 18 October 2004 05:03 pm, James Bottomley wrote:
> Matthew Wilcox:
> o Add SPI-5 constants to scsi.h
This breaks Firewire SBP2 build:
CC [M] drivers/ieee1394/sbp2.o
In file included from drivers/ieee1394/sbp2.c:78:
drivers/ieee1394/sbp2.h:61:1: warning: "ABORT_TASK_SET" redefined
In file included from drivers/scsi/scsi.h:31,
from drivers/ieee1394/sbp2.c:67:
include/scsi/scsi.h:255:1: warning: this is the location of the previous definition
In file included from drivers/ieee1394/sbp2.c:78:
drivers/ieee1394/sbp2.h:62:1: warning: "LOGICAL_UNIT_RESET" redefined
In file included from drivers/scsi/scsi.h:31,
from drivers/ieee1394/sbp2.c:67:
include/scsi/scsi.h:267:1: warning: this is the location of the previous definition
It looks like firewire has its own set of commands with conflicting names.
Who should win?
--
Dmitry
next prev parent reply other threads:[~2004-10-19 4:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 22:03 [BK PATCH] SCSI updates for 2.6.9 James Bottomley
2004-10-18 22:03 ` James Bottomley
2004-10-19 0:30 ` K.R. Foley
2004-10-19 4:41 ` Dmitry Torokhov [this message]
2004-10-19 5:05 ` Andrew Morton
2004-10-19 5:12 ` Dmitry Torokhov
2004-10-19 7:13 ` Linus Torvalds
2004-10-19 7:42 ` Ben Collins
2004-10-19 8:03 ` Jens Axboe
2004-10-19 13:54 ` James Bottomley
2004-10-19 16:17 ` Matthew Wilcox
2004-10-20 23:22 ` Douglas Gilbert
2004-10-22 17:52 ` Linus Torvalds
2004-10-22 19:46 ` James Bottomley
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=200410182341.13648.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=torvalds@osdl.org \
--cc=willy@debian.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.