From: Greg KH <greg@kroah.com>
To: Martin Hicks <mort@wildopensource.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
jgarzik@pobox.com, linux-scsi@vger.kernel.org,
Jesse Barnes <jbarnes@sgi.com>,
jeremy@sgi.com
Subject: Re: [PATCH] SATA Transport Attributes
Date: Mon, 29 Mar 2004 17:16:27 -0800 [thread overview]
Message-ID: <20040330011626.GA8647@kroah.com> (raw)
In-Reply-To: <20040330004601.GE18948@localhost>
On Mon, Mar 29, 2004 at 07:46:01PM -0500, Martin Hicks wrote:
>
> Hello,
>
> Here is a patch that introduces a Transport Attribute class for SATA
> devices. The patch also includes an update to the Vitesse driver to use
> the transport attribute.
>
> The only problem that I'm having right now is that sometimes I get
> a NULL pointer dereference in scsi_remove_device() when I rmmod sata_vsc.
There's a nasty sysfs "issue" right now that can cause this to happen.
See the thread about it on lkml for more details. This might be causing
your oops.
thanks,
greg k-h
next prev parent reply other threads:[~2004-03-30 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 0:46 [PATCH] SATA Transport Attributes Martin Hicks
2004-03-30 1:16 ` Greg KH [this message]
2004-03-30 1:23 ` Jeff Garzik
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=20040330011626.GA8647@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@steeleye.com \
--cc=jbarnes@sgi.com \
--cc=jeremy@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mort@wildopensource.com \
/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