public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Adam Radford <aradford@amcc.com>
Cc: Peter Daum <gator@cs.tu-berlin.de>, linux-kernel@vger.kernel.org
Subject: Re: 3ware driver (3w-xxxx) in 2.6.10: procfs entry
Date: Wed, 19 Jan 2005 11:09:02 +0000	[thread overview]
Message-ID: <20050119110902.GA12903@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0501101452590.14606-100000@swamp.bayern.net>

> > > It looks like in the 3ware driver the procfs entry "/proc/scsi/3w-xxxx"
> > > has been removed (or actually moved to sysfs).
> > > Unfortunately, this breaks all the (binary only )-: tools provided by
> > > 3ware, which are indispensable for system maintenance.
> >
> > The change came from the driver maintainer at 3ware.  Get the updated
> > tools from their website.
> 
> Which website do you mean? The programs in the download section of
> "www.3ware.com" are just the ones that don't work anymore.

It's there just a little hidden.  Adam, any chance the new managment tools
could be placed more promimently on the website?


  parent reply	other threads:[~2005-01-19 11:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 13:03 3ware driver (3w-xxxx) in 2.6.10: procfs entry Peter Daum
2005-01-10 13:21 ` Christoph Hellwig
2005-01-10 13:56   ` Peter Daum
2005-01-10 16:45     ` Andrey Klochko
2005-01-10 17:21     ` Ricky Beam
2005-01-17  3:52       ` Chris Caputo
2005-01-19 11:09     ` Christoph Hellwig [this message]
2005-01-19 12:33       ` Peter Daum
2005-01-20  2:23         ` Jason L Tibbitts III
2005-01-20  4:38           ` Kyle Moffett
     [not found]             ` <ufais5s4sdk.fsf@epithumia.math.uh.edu>
2005-01-20  4:57               ` Kyle Moffett
2005-02-09  8:41         ` Peter Daum
2005-02-09  9:57           ` Peter Daum

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=20050119110902.GA12903@infradead.org \
    --to=hch@infradead.org \
    --cc=aradford@amcc.com \
    --cc=gator@cs.tu-berlin.de \
    --cc=linux-kernel@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