public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: war <war@starband.net>
To: linux-kernel@vger.kernel.org
Subject: [Fwd: 2.4.16 Bug (PPC)]
Date: Mon, 26 Nov 2001 13:50:15 -0500	[thread overview]
Message-ID: <3C028EE7.B9C07F8E@starband.net> (raw)

Tom Rini wrote:

> On Mon, Nov 26, 2001 at 01:22:37PM -0500, war wrote:
>
> > This is the actual SCSI driver I need for the 7200/90.
>
> What card did you throw in that box?  By default you'd want CONFIG_SCSI_MESH
> (internal) and CONFIG_SCSI_MAC53C94 (external).  For the ncr53c8xx stuff
> you would want CONFIG_SCSI_NCR53C8XX (low #s) or the sym_2 driver.
>
> > cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
> > -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
> > -D__powerpc__ -fsigned-char -msoft-float -pipe -ffixed-r2
> > -Wno-uninitialized -mmultiple -mstring    -c -o 53c7,8xx.o 53c7,8xx.c
> > 53c7,8xx.c: In function `ncr_pci_init':
> > 53c7,8xx.c:1436: `is_prep' undeclared (first use in this function)
> > 53c7,8xx.c:1436: (Each undeclared identifier is reported only once
> > 53c7,8xx.c:1436: for each function it appears in.)
>
> I just fixed this for 2.2.20, so I'll do it for 2.4.16 shortly and
> submit to marcelo/maintainer of this file..  In short, 'is_prep' is
> bogus and should be (_machine == _MACH_prep).
>
> --
> Tom Rini (TR1265)
> http://gate.crashing.org/~trini/


             reply	other threads:[~2001-11-26 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 18:50 war [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-26 18:46 [Fwd: 2.4.16 Bug (PPC)] war

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=3C028EE7.B9C07F8E@starband.net \
    --to=war@starband.net \
    --cc=linux-kernel@vger.kernel.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