From: Arnd Bergmann <arnd@arndb.de>
To: linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: s390 patches: descriptions.
Date: Fri, 26 Sep 2003 13:51:38 +0200 [thread overview]
Message-ID: <200309261347.25861.arnd@arndb.de> (raw)
> Hi Pete,
>
> > Are you going to submit zfcp and zcrypt and if yes, when?
>
> The zfcp rework is going well but isn't quite finished yet.
> It's up to Heiko when he consideres the driver to be in state
> for inclusion into 2.6. For the zcrypt driver the news aren't
> so good. It very likely won't make it for 2.6.0.
Actually, the latest z90crypt driver for 2.4.21 compiles on 2.6
with only one trivial patch (see below). The chances are good
that it works just as much as on older kernels. It's mostly
just a matter of style and the fact that there is no standard
API for linux hardware crypto driver yet that keeps us from
submitting the driver.
Arnd <><
diff -u ../linux-2.3/drivers/s390/misc/z90main.c drivers/s390/misc/z90main.c
--- ../linux-2.3/drivers/s390/misc/z90main.c 2003-08-18 18:51:14.000000000 +0200
+++ drivers/s390/misc/z90main.c 2003-09-26 13:15:49.000000000 +0200
@@ -567,7 +567,6 @@
int result,nresult;
struct proc_dir_entry * entry;
- EXPORT_NO_SYMBOLS;
PDEBUG("init_module -> PID %d\n", PID());
//
next reply other threads:[~2003-09-26 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 11:51 Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-26 14:38 s390 patches: descriptions Martin Schwidefsky
2003-09-26 14:16 Martin Schwidefsky
2003-09-26 9:32 Martin Schwidefsky
2003-09-26 13:43 ` Pete Zaitcev
[not found] <mailman.1064510341.19756.linux-kernel2news@redhat.com>
2003-09-26 0:48 ` Pete Zaitcev
2003-09-25 17:14 Martin Schwidefsky
2003-09-25 17:54 ` Sam Ravnborg
2003-09-11 17:13 s390 patches: Descriptions Martin Schwidefsky
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=200309261347.25861.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=zaitcev@redhat.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