linux-kernel - Re: [build bug] drivers/scsi/NCR53C9x.c:913: error: 'Scsi_Cmnd' has no member named 'use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64N.0802041045500.23236@blysk.ds.pg.gda.pl>
Date:	Mon, 4 Feb 2008 11:01:22 +0000 (GMT)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Boaz Harrosh <bharrosh@...asas.com>
cc:	Ingo Molnar <mingo@...e.hu>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	James Bottomley <James.Bottomley@...elEye.com>,
	linux-kernel@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>
Subject: Re: [build bug] drivers/scsi/NCR53C9x.c:913: error: 'Scsi_Cmnd' has
 no member named 'use_sg'

On Thu, 31 Jan 2008, Boaz Harrosh wrote:

> On Thu, Jan 31 2008 at 19:29 +0200, Ingo Molnar <mingo@...e.hu> wrote:
> > FYI, automated testing found the following build breakage:
> > 
> > drivers/scsi/NCR53C9x.c: In function 'esp_get_dmabufs':
> > drivers/scsi/NCR53C9x.c:913: error: 'Scsi_Cmnd' has no member named 'use_sg'
> > drivers/scsi/NCR53C9x.c:914: error: 'Scsi_Cmnd' has no member named 'request_bufflen'
> > 
> > config attached.
> > 
> > 	Ingo
> > 
> Cc linux-scsi mailing list.
> 
> This driver and others are scheduled to be removed in the scsi-pending tree
> and are awaiting ACKs from - disappeared - maintainers.

 Well, buried in some other activities.  You certainly have had my ack to 
remove dec_esp.c already and I started to work on replacement front-end 
drivers long ago.

 Unfortunately one of the three hardware configurations to be supported by 
the front-ends does not fit the interrupt handling model implemented by 
the esp_scsi.c core.  Or it is actually the other way round as you cannot 
adjust hardware to fit the driver, so I am in a process of rewriting the 
core a little bit in this respect -- the core switches to interrupt 
polling under some circumstances and does not expect a higher-priority 
interrupt of a different kind to arrive from the bus master controller the 
SCSI chips are attached to instead.

 Being no SCSI expert though I have to study the SCSI spec well enough to 
understand some bits and I am somewhat distracted these days, so it may 
take a while yet.  It is at the highest priority on my to-do list though.

  Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/