linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Eisenbud <eisenbud@cs.swarthmore.edu>
To: Paul Mackerras <paulus@linuxcare.com.au>
Cc: LinuxPPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: SOLVED: mesh SCSI bus locks hard on 7500 when burning a CD-R in dao mode
Date: Sat, 3 Feb 2001 11:27:05 -0500	[thread overview]
Message-ID: <20010203112705.A19223@allspice.cs.swarthmore.edu> (raw)
In-Reply-To: <20010203111427.B15855@allspice.cs.swarthmore.edu>; from eisenbud@cs.swarthmore.edu on Sat, Feb 03, 2001 at 11:14:27AM -0500


On Sat, Feb 03, 2001 at 11:14:27AM -0500, Daniel Eisenbud <eisenbud@cs.swarthmore.edu> wrote:
> On Sat, Feb 03, 2001 at 03:19:18PM +1100, Paul Mackerras <paulus@linuxcare.com.au> wrote:
[...]
> > Well, it could be declared in scsi.h but the actual table of values
> > should go in a .c file.
>
> My current patch has a static function in the new file scsi_dataout.h,
> which is included by all the drivers in question.   But I agree that it
> would be cleaner to declare the function in scsi.h, change
> scsi_dataout.h to scsi_dataout.c, make the function no longer static,
> and tell make about the dependencies.  I'll do that.

The advantage of my current approach is that there are two SCSI drivers
(for acorn and i2o) that use copies of this table but that live outside
of drivers/scsi.  They already include scsi.h, and it's easy to make
them include scsi_dataout.h.  For the files inside drivers/scsi, it's
easy to see how to make them depend on scsi_dataout.o, but it's not
obvious to me how it should work for files that live elsewhere.  Am I
missing something obvious?

-Daniel

--
Daniel E. Eisenbud
eisenbud@cs.swarthmore.edu

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-02-03 16:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 19:48 mesh SCSI bus locks hard on 7500 when burning a CD-R in dao m ode Amit Chaudhary
2001-01-26 20:12 ` Daniel Eisenbud
2001-01-26 20:50   ` Michael Schmitz
2001-01-26 21:04     ` mesh SCSI bus locks hard on 7500 when burning a CD-R in dao mode Daniel Eisenbud
2001-01-26 21:32       ` Michael Schmitz
2001-01-27 21:31         ` Daniel Eisenbud
2001-01-28  0:59           ` Daniel Eisenbud
2001-01-28  1:25             ` Daniel Eisenbud
2001-01-28  2:34               ` Daniel Eisenbud
2001-01-28  5:09                 ` Daniel Eisenbud
2001-01-28  5:11                   ` Daniel Eisenbud
2001-01-28  7:16                     ` Daniel Eisenbud
2001-01-28  7:17                       ` Daniel Eisenbud
2001-01-28 20:24                         ` scsi debug info before and after mesh locks up Daniel Eisenbud
2001-01-29 14:29             ` mesh SCSI bus locks hard on 7500 when burning a CD-R in dao mode Michael Schmitz
2001-01-29 23:20               ` Daniel Eisenbud
2001-01-30 21:28                 ` Michael Schmitz
2001-01-30 21:35                   ` Daniel Eisenbud
2001-01-30 21:46                     ` Michael Schmitz
2001-01-30 21:57                       ` Daniel Eisenbud
2001-01-31 16:40                         ` Chris Boot
2001-02-01 16:50                           ` Daniel Eisenbud
2001-02-02  7:38                             ` SOLVED: " Daniel Eisenbud
2001-02-02 12:58                               ` Michael Schmitz
2001-02-02 15:14                                 ` Daniel Eisenbud
2001-02-05 12:41                                 ` Benjamin Herrenschmidt
2001-02-03  4:19                               ` Paul Mackerras
2001-02-03 16:14                                 ` Daniel Eisenbud
2001-02-03 16:27                                   ` Daniel Eisenbud [this message]
2001-02-03 18:48                                     ` PATCH: " Daniel Eisenbud
2001-02-04 21:37                                 ` SOLVED: " Michael Schmitz
2001-02-05  8:28                                   ` Geert Uytterhoeven
2001-01-31  7:10                       ` Geert Uytterhoeven
2001-01-29 14:28           ` Michael Schmitz

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=20010203112705.A19223@allspice.cs.swarthmore.edu \
    --to=eisenbud@cs.swarthmore.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@linuxcare.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).