From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: s390 patches for 2.6.5-rc1-mm1.
Date: Tue, 16 Mar 2004 14:48:52 +0100 [thread overview]
Message-ID: <20040316134852.GA2785@mschwid3.boeblingen.de.ibm.com> (raw)
Hi Andrew,
the current set of s390 patches against 2.6.5-rc1-mm1. The differ a bit
from the last set I sent:
> Short descriptions:
> 1) s390 architecture fixes. This one clashes with the remap-file-pages
> fix for s390 I sent yesterday but the conflict is easy to fix.
> 2) Some more common i/o layer fixes.
> 3) Fix for the last sclp fix.
> 4) Network driver fixes.
> 5) Dasd driver fixes.
> 6) z/VM monitor stream fixes.
> 7) Tape driver fixes.
> 8) The real zfcp bug fixes.
> 9) zfcp host adapter message cleanup part 1.
> 10) zfcp host adapter message cleanup part 2.
Changes 16.03.2004
1) added another single stepped svc patch, applies on top of remap-file-pages
2) added activity check fix
4) added code to allow to change the netiucv peer username
7) adapted to recent bk changes
8) added include file cleanup & small optimization.
Protests against the zfcp patch #8 have died down. I still think the kfree
trick is the best solution for the port/unit object release problem.
Perhaps we'll see some more feedback from the linux-scsi list.
That leaves the question whether we could use dev_printk instead of the
ZFCP_LOG macros. dev_printk doesn't offer a variable log level, so the
one macro can't just be replaced by another. For now, I'd say no.
blue skies,
Martin.
reply other threads:[~2004-03-16 14:11 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=20040316134852.GA2785@mschwid3.boeblingen.de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®