public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Dmitry Meshchaninov <dima@flash.datafoundation.com>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com,
	alan@lxorguk.ukuu.org.uk, cwl@iol.unh.edu,
	Denis Gerasimov <denis@datafoundation.com>
Subject: Re: qlogicfc driver
Date: Fri, 29 Jun 2001 17:41:44 -0400	[thread overview]
Message-ID: <3B3CF618.DDE40F17@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0106291714470.11344-100000@flash.datafoundation.com>

Dmitry Meshchaninov wrote:
> 
>   Hi!
>   Judging from recent messages on linux-kernel and from the code which is
> currently in 2.4.x the qlogicfc driver needs to be updated a bit. I have
> done some amount of work on this driver and have sent patches to
> Chris in the past, however I did not receive any comments on my changes.
> It looks like Chris is too busy with other things right now, and I will
> gladly maintain the driver if there is a consensus that the driver needs
> a new maintainer. Meanwhile I am cleaning up driver for 2.4.4
> (not tested with 2.4.5 yet, but probably will work). I'll publish those
> changes if there will be any interest.  It is a  drop-in replacement for
> the five files in drivers/scsi/ (qlogicfc.c, qlogicfc.h, qlogicfc_inc.h,
> qlogicfc_asm_ip.c and qlogicfc_asm.c).  This contains updated (both with
> and without ip support) firmware and many bugfixes. I decided not to
> provide a patch because it is bigger then just those five files combind.
> I have splitted up driver body into .h-file with types&defines  and
> driver itself (as it should be). But this is negotiable.

If you are working on qlogicfc, that's great!

But since others are currently using this driver without problems, you
might consider sending in your patches separated out (per
Documentation/SubmittingPatches) so that it is easier for others to
review and apply them in turn.

-- 
Jeff Garzik      | Andre the Giant has a posse.
Building 1024    |
MandrakeSoft     |

  reply	other threads:[~2001-06-29 21:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29 21:33 qlogicfc driver Dmitry Meshchaninov
2001-06-29 21:41 ` Jeff Garzik [this message]
2001-06-29 21:59   ` David S. Miller
2001-07-02  8:19     ` christophe barbé
  -- strict thread matches above, loose matches on Subject: below --
2001-07-26 13:37 Roland Fehrenbacher
2001-07-26 13:32 Roland Fehrenbacher
2001-07-20 21:01 Roland Fehrenbacher
2001-07-20 22:15 ` jsack
2001-07-20 16:20 Roland Fehrenbacher
2001-07-20 15:40 Roland Fehrenbacher
2001-06-01  9:20 christophe barbé

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=3B3CF618.DDE40F17@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cwl@iol.unh.edu \
    --cc=denis@datafoundation.com \
    --cc=dima@flash.datafoundation.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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