linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi host/scsi device ref count cleanup 3/4
Date: Sun, 13 Jul 2003 14:39:32 +0100	[thread overview]
Message-ID: <20030713143932.B24729@infradead.org> (raw)
In-Reply-To: <20030710140340.GA3336@beaverton.ibm.com>; from andmike@us.ibm.com on Thu, Jul 10, 2003 at 07:03:40AM -0700

On Thu, Jul 10, 2003 at 07:03:40AM -0700, Mike Anderson wrote:
> > Can you explain why we don't need that anymore?  /me wants to learn a bit
> > more about deep LDM magic..
> > 
> 
> I do not know if I can reveal the magic as some of this is bread crumbs
> created by previous bad paths taken :-).

Hehe.

> I think SCSI core has unique issues stuck between the bus layer struct
> device LDM registration and the block layer pure kobjects.
> 
> I removed the class get/puts to simplify the scsi_host_get code and
> reduce ordering problems between the class and device release methods.
> We could have chosen either the structure device or the class device to
> ref count on. The struct device appears to be a better object to ref
> count against as it is the child of the adapter struct device and the
> parent of the scsi device struct device.

Agreed.  What do we need the classdev for at all?

> ok I created a wrapper function called scsi_device_cancel_cb (seems like
> others where using callback but that seemed to long).

or just name it cancel_callback (I assume it's static)

> > Shouldn't these better be printed in ascii instead of the binary
> > presentation that might aswell change form one kernelrelease to
> > another?
> > 
> 
> Yes, I was lazy and did this initially for debug. Do have a suggested
> format (i.e., comma separated or colon separated or ??).

coma separated looks fine to me.

> 
> Yes it should. I made this a separate patch in the series
> in case Matthew / Alan see other changes needed with usb storage
> shutdown.

Ok.


  reply	other threads:[~2003-07-13 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 22:24 [PATCH] scsi host/scsi device ref count cleanup 0/4 Mike Anderson
2003-07-08 22:25 ` [PATCH] scsi host/scsi device ref count cleanup 1/4 Mike Anderson
2003-07-08 22:26   ` [PATCH] scsi host/scsi device ref count cleanup 2/4 Mike Anderson
2003-07-08 22:27     ` [PATCH] scsi host/scsi device ref count cleanup 3/4 Mike Anderson
2003-07-08 22:27       ` [PATCH] scsi host/scsi device ref count cleanup 4/4 Mike Anderson
2003-07-09  8:15         ` (unknown) Christoph Hellwig
2003-07-09  7:53       ` [PATCH] scsi host/scsi device ref count cleanup 3/4 Christoph Hellwig
2003-07-10 14:03         ` Mike Anderson
2003-07-13 13:39           ` Christoph Hellwig [this message]
2003-07-09  7:39     ` [PATCH] scsi host/scsi device ref count cleanup 2/4 Christoph Hellwig

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=20030713143932.B24729@infradead.org \
    --to=hch@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).