Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261259AbVDUKJr (ORCPT ); Thu, 21 Apr 2005 06:09:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261243AbVDUKJr (ORCPT ); Thu, 21 Apr 2005 06:09:47 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:49580 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S261250AbVDUKJf (ORCPT ); Thu, 21 Apr 2005 06:09:35 -0400 Date: Thu, 21 Apr 2005 11:09:33 +0100 From: Christoph Hellwig To: Geert Uytterhoeven Cc: "James E.J. Bottomley" , Linux Kernel Development , linux-scsi@vger.kernel.org, Linux/m68k Subject: Re: [PATCH] kill old EH constants Message-ID: <20050421100933.GA19586@infradead.org> Mail-Followup-To: Christoph Hellwig , Geert Uytterhoeven , "James E.J. Bottomley" , Linux Kernel Development , linux-scsi@vger.kernel.org, Linux/m68k References: <200504210608.j3L682Br002585@hera.kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 825 Lines: 23 On Thu, Apr 21, 2005 at 11:58:12AM +0200, Geert Uytterhoeven wrote: > sun3_NCR5380.c still uses the following: > > - SCSI_ABORT_SUCCESS > - SCSI_ABORT_ERROR > - SCSI_ABORT_SNOOZE > - SCSI_ABORT_BUSY > - SCSI_ABORT_NOT_RUNNING > - SCSI_RESET_SUCCESS > - SCSI_RESET_BUS_RESET > > causing the driver to fail to build in 2.6.12-rc3. What should I replace them > by? You must replace NCR5380_abort and NCR5380_bus_reset with real new-style EH routines. I'd suggest copying them from NCR5380.c or even better scrapping sun3_NCR5380.c in favour of that one completely. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/