linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: FUJITA Tomonori <tomof@acm.org>
To: James.Bottomley@SteelEye.com
Cc: fujita.tomonori@lab.ntt.co.jp, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_transport_sas: add destructor for bsg
Date: Sat, 21 Jul 2007 01:51:35 +0900	[thread overview]
Message-ID: <20070721013005K.tomof@acm.org> (raw)
In-Reply-To: <1184947805.3455.21.camel@localhost.localdomain>

From: James Bottomley <James.Bottomley@SteelEye.com>
Subject: [PATCH] scsi_transport_sas: add destructor for bsg
Date: Fri, 20 Jul 2007 11:10:05 -0500

> There's currently no destructor for the bsg components.  If you insert
> and remove the module, you see the bsg devices building up and up.  This
> patch adds the destructor in the correct place in the transport class so
> that the bsg and request queue are removed just before the device
> destruction.

Thanks. Sorry about the silly bug.

      reply	other threads:[~2007-07-20 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 16:10 [PATCH] scsi_transport_sas: add destructor for bsg James Bottomley
2007-07-20 16:51 ` FUJITA Tomonori [this message]

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=20070721013005K.tomof@acm.org \
    --to=tomof@acm.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --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).