From: Jamie Lenehan <lenehan@twibble.org>
To: linux-scsi@vger.kernel.org
Cc: dc395x@twibble.org
Subject: dc395x updated for latest bk
Date: Wed, 11 Jun 2003 18:00:39 +1000 [thread overview]
Message-ID: <20030611080039.GA2064@twibble.org> (raw)
For anyone using this driver some changes have been included (pushed
by Oliver) in the main bk tree. I've re-created all my outstanding
patches against 2.5.70-bk9 and tested it against 2.5.70-bk9 and
2.5.70-bk15.
Available in the usual place:
http://twibble.org/dist/dc395x/
No new changes have been added. It's too time consuming to rediff as
things change so I'm waiting until all the existing changes get
included before making any more changes.
The included changes were:
2.5.70-bk1 included the sharded IRQ crashing fix
(00-irq-crash-fix.patch) with some minor NULL/whitepsace
changes.
2.5.70-bk9 included the debugging cleanup (01-debug-cleanup.patch),
the module cleanup (02-module-cleanup.patch), some
changes from linux-scsi to the proc function (hch) and a
lot of unrelated white space and for/while conversions.
--
Jamie Lenehan Work Phone: +61 3 9843 8817
lenehan@twibble.org Work Email: jamie.lenehan@activcard.com.au
reply other threads:[~2003-06-11 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030611080039.GA2064@twibble.org \
--to=lenehan@twibble.org \
--cc=dc395x@twibble.org \
--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