public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "C.Newport" <crn@netunix.com>
To: "David S. Miller" <davem@redhat.com>, Christoph Hellwig <hch@lst.de>
Cc: linux-scsi@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: future of drivers/fc4/
Date: Sun, 20 Jun 2004 21:05:00 +0100	[thread overview]
Message-ID: <200406202105.00577.crn@netunix.com> (raw)
In-Reply-To: <20040620114010.73f1b98a.davem@redhat.com>

On Sunday 20 June 2004 7:40 pm, David S. Miller wrote:
> On Sun, 20 Jun 2004 18:03:53 +0200
>
> Christoph Hellwig <hch@lst.de> wrote:
> > The SUN FCAL support has been non-working for ages and needs major work
> > to keep up with scsi API changes.  Is anyone planning to ressurect it
> > midterm?  If not I'd like to remove it from the tree.
>
> Feel free to remove it, interested parties can resurrect the source
> really easily.

If it is that easy could someone tell me what needs doing please ?
I am NOT a kernel programmer but given a little handholding and
a list of what to do I can build and test it here.

I also have a spare set of hardware if someone in the UK with the
needed skills would like it. Sorry, but the disk array is a bit heavy to 
ship elsewhere. If someone already has the array I will mail a card
anywhere.

We need this if we are ever to get the Sun4D working again.
Keith now has a contact for the missing info to get Sun4D working
properly, but without the fc, soc and pluto it will be rather restricted in
usefulness.

 

      reply	other threads:[~2004-06-20 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 16:03 future of drivers/fc4/ Christoph Hellwig
2004-06-20 18:40 ` David S. Miller
2004-06-20 20:05   ` C.Newport [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=200406202105.00577.crn@netunix.com \
    --to=crn@netunix.com \
    --cc=davem@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sparclinux@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