From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-scsi@vger.kernel.org
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: [PATCH 2.4 0/2] Fix cpqfc
Date: Mon, 2 Jan 2006 12:44:34 +0100 [thread overview]
Message-ID: <200601021244.40636@bilbo.math.uni-mannheim.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
As there are still people out there trying their luck with the ancient cpqfc
driver that is in 2.4 kernel I think we should make this a bit less buggy.
The next 2 patches don't change the driver behavior but reduce stack usage
and make sure not to copy foreign stack memory.
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-01-02 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 11:44 Rolf Eike Beer [this message]
2006-01-02 11:56 ` [PATCH 2.4 1/2] Fix cpqfc::cpqfcTSPutLinkQue() Rolf Eike Beer
2006-01-02 12:05 ` [PATCH 2.4 2/2] cpqfc: Reduce stack usage of 2 functions Rolf Eike Beer
2006-01-03 10:29 ` Marcelo Tosatti
2006-01-03 13:51 ` Rolf Eike Beer
2006-01-03 11:59 ` Marcelo Tosatti
2006-01-03 14:28 ` Rolf Eike Beer
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=200601021244.40636@bilbo.math.uni-mannheim.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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