public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-scsi@vger.kernel.org, garloff@suse.de, gl@dsa-ac.de
Subject: Re: [PATCH] Re: AMD 53c974 SCSI driver in 2.6
Date: Mon, 3 Nov 2003 09:14:51 +0000	[thread overview]
Message-ID: <20031103091451.A25391@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0311021933100.4615-100000@poirot.grange>; from g.liakhovetski@gmx.de on Sun, Nov 02, 2003 at 08:22:23PM +0100

On Sun, Nov 02, 2003 at 08:22:23PM +0100, Guennadi Liakhovetski wrote:
> Ok, started looking at the tmscsim. A couple of questions:
> 
> 1) After the "next" element has disappeared from the struct scsi_cmnd,
> what is the "correct" / preferred way to queue scsi commands in drivers?
> I saw aic7xxx (new) casting a part of struct scsi_pointer SCp in
> scsi_cmnd, starting from Status to a list_head (or an anology thereof),
> which doesn't seem very nice. Anyway, I didn't find any "standard" way for
> doing this. Should host_scribble be used?

Just overlay your own structure over the scsi_pointer - you can easily
embedd a list_head in there.  But in 2.6 a driver really schouldn't need
to keep it's own list anyway :)

> 2) Actually, which scsi driver (or, better, several drivers) can be
> considered well-written and can be taken as examples? I tried looking at
> aic7xxx, as it is a pretty new one, but I am not sure if it is really a
> good example to follow and it is pretty big too.

aic7xxx is a very bad example.  It's a BSDish driver glued into Linux.
I'd suggest looking into qla1280 or the 53c700 driver and it's glue
drivers instead. In qla1280 you can also see an example for the above
embedding, looks for struct srb.

> P.S. Should this thread be taken to linux-scsi or is it better to continue
> it on lkml?

I think linux-scsi is the right list, and dropped the lkml Cc.

-- 
Christoph Hellwig <hch@lst.de>		-	Freelance Hacker
Contact me for driver hacking and kernel development consulting

  reply	other threads:[~2003-11-03  9:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031031114616.A16435@infradead.org>
2003-11-02 19:22 ` [PATCH] Re: AMD 53c974 SCSI driver in 2.6 Guennadi Liakhovetski
2003-11-03  9:14   ` Christoph Hellwig [this message]
2003-11-15 21:48     ` Guennadi Liakhovetski
2003-11-17  0:03       ` Guennadi Liakhovetski
2003-11-17 21:41         ` Randy.Dunlap
2003-11-17 22:42           ` Guennadi Liakhovetski
2003-11-17 23:14             ` Randy.Dunlap
2003-11-17 23:28               ` Kurt Garloff
2003-11-17 23:31                 ` Randy.Dunlap
2003-11-18  0:04                 ` Guennadi Liakhovetski
     [not found]               ` <Pine.LNX.4.44.0311180049250.2258-200000@poirot.grange>
2003-11-18  9:28                 ` Kurt Garloff
2003-11-18 10:22                   ` Guennadi Liakhovetski
2003-11-18 23:07                   ` Guennadi Liakhovetski
2003-11-19 15:34                     ` Kurt Garloff
2003-11-20 11:37                       ` Guennadi Liakhovetski
2003-11-20 22:57                         ` TMSCSIM [2.6] (was: Re: [PATCH] Re: AMD 53c974 SCSI driver in 2.6) Guennadi Liakhovetski
2003-11-22 23:23                           ` Guennadi Liakhovetski
2003-11-22 23:27                           ` Guennadi Liakhovetski
2003-11-23 20:26                             ` TMSCSIM [2.6] Matthias Andree
2003-11-23 20:53                               ` Guennadi Liakhovetski
2003-11-23 23:29                               ` Kurt Garloff
2003-11-24  7:47                             ` TMSCSIM [2.6] (was: Re: [PATCH] Re: AMD 53c974 SCSI driver in 2.6) Christoph Hellwig
2003-11-24 20:18                               ` Guennadi Liakhovetski

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=20031103091451.A25391@infradead.org \
    --to=hch@infradead.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=garloff@suse.de \
    --cc=gl@dsa-ac.de \
    --cc=linux-scsi@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