From: christof.schmitt@de.ibm.com
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [patch 00/11] zfcp updates for 2.6.27
Date: Mon, 30 Jun 2008 12:52:36 +0200 [thread overview]
Message-ID: <20080630105236.960064000@de.ibm.com> (raw)
James,
here are the final large zfcp updates for 2.6.27.
The first patches are small fixes for problems that were found with
the last updates. One patch moves the helper functions for the
scsi_cmnd status to the common scsi include file. The last patches are
the large code cleanups.
The patches apply to current scsi-misc.
Christof
next reply other threads:[~2008-06-30 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 10:52 christof.schmitt [this message]
2008-06-30 10:52 ` [patch 01/11] zfcp: wait until adapter is finished with ERP during auto-port christof.schmitt
2008-06-30 10:52 ` [patch 02/11] zfcp: Fix error checking for ELS ADISC requests christof.schmitt
2008-06-30 10:52 ` [patch 03/11] zfcp: Adapter reopen for large number of unsolicited status christof.schmitt
2008-06-30 10:52 ` [patch 04/11] zfcp: Small QDIO cleanups christof.schmitt
2008-06-30 10:52 ` [patch 05/11] zfcp: Move status accessors from zfcp to SCSI include file christof.schmitt
2008-06-30 10:52 ` [patch 06/11] zfcp: Cleanup of code in zfcp_scsi.c christof.schmitt
2008-06-30 10:52 ` [patch 07/11] zfcp: Cleanup of code in zfcp_aux.c christof.schmitt
2008-06-30 22:52 ` Heiko Carstens
2008-07-01 13:44 ` Swen Schillig
2008-07-02 7:03 ` Christof Schmitt
2008-06-30 10:52 ` [patch 08/11] zfcp: consolidate sysfs things into one file christof.schmitt
2008-06-30 10:52 ` [patch 09/11] zfcp: zfcp_fsf cleanup christof.schmitt
2008-06-30 10:52 ` [patch 10/11] zfcp: Cleanup code in zfcp_erp.c christof.schmitt
2008-06-30 10:52 ` [patch 11/11] zfcp: Cleanup external header file christof.schmitt
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=20080630105236.960064000@de.ibm.com \
--to=christof.schmitt@de.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-s390@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