From: Bart Van Assche <bart.vanassche@sandisk.com>
To: James Bottomley <jbottomley@odin.com>
Cc: Christoph Hellwig <hch@lst.de>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Hannes Reinecke <hare@suse.de>,
Mike Christie <michaelc@cs.wisc.edu>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
target-devel <target-devel@vger.kernel.org>
Subject: [PATCH v3] Split SCSI header files
Date: Tue, 7 Apr 2015 14:32:21 +0200 [thread overview]
Message-ID: <5523CE55.3090401@sandisk.com> (raw)
Move the constants and functions that are used by both initiator and
target code to new header files such that the target code does no longer
have to include initiator header files.
Changes in v3 of this series compared to v2:
- Renamed scsi_lib.h into scsi_common.h.
- Added a patch for replacing MAX_COMMAND_SIZE with BLK_MAX_CDB.
- Added a patch that minimizes the include directives in target code.
Changes in v2 of this series compared to v1:
- Dropped the scsi_lun.h header file and introduced scsi_lib.h.
The patches in this series are:
0001-Split-SCSI-header-files.patch
0002-Replace-MAX_COMMAND_SIZE-with-BLK_MAX_CDB.patch
0003-target-Correct-a-comment.patch
0004-target-Minimize-SCSI-header-include-directives.patch
next reply other threads:[~2015-04-07 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 12:32 Bart Van Assche [this message]
2015-04-07 12:33 ` [PATCH v3 1/4] Split SCSI header files Bart Van Assche
2015-04-07 12:33 ` [PATCH v3 2/4] Replace MAX_COMMAND_SIZE with BLK_MAX_CDB Bart Van Assche
2015-04-07 12:33 ` [PATCH v3 3/4] target: Correct a comment Bart Van Assche
2015-04-07 12:34 ` [PATCH v3 4/4] target: Minimize SCSI header #include directives Bart Van Assche
2015-04-13 9:44 ` [PATCH v3] Split SCSI header files Christoph Hellwig
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=5523CE55.3090401@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jbottomley@odin.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=target-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.