From: "Love, Robert W" <robert.w.love@intel.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: fcoe pull request for 3.12(+)
Date: Thu, 5 Sep 2013 19:12:44 +0000 [thread overview]
Message-ID: <5228D7AC.9050904@intel.com> (raw)
The following changes since commit 6e4664525b1db28f8c4e1130957f70a94c19213e:
Linux 3.11 (2013-09-02 13:46:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rwlove/fcoe.git tags/show
for you to fetch changes up to 1c2c1b4fbd413fd814807768d2aba9023722ed76:
fcoe: Reduce fcoe_sysfs_fcf_add() stack usage (2013-09-04 14:14:21 -0700)
----------------------------------------------------------------
Pull request tag for 3.12 merge window.
----------------------------------------------------------------
Bart Van Assche (13):
libfc: Source code comment spelling fixes
libfc: Debug code fixes
libfc: Micro-optimize fc_setup_exch_mgr()
libfc: Clarify fc_exch_find()
libfc: Fix a race in fc_exch_timer_set_locked()
libfc: Protect ep->esb_stat changes via ex_lock
libfc: Avoid that sending after an abort triggers a kernel warning
libfc: Reduce exchange lock contention in fc_exch_recv_abts()
libfc: Do not invoke the response handler after fc_exch_done()
fcp: Do not interpret check condition as underrun
fcoe: Declare fcoe_ctlr_mode_set() static
fcoe: Add missing newlines in debug messages
fcoe: Reduce fcoe_sysfs_fcf_add() stack usage
Neil Horman (3):
fcoe: ensure that skb placed on the fip_recv_list are unshared
fcoe: make sure fcoe frames are unshared prior to manipulating them
fcoe: cleanup return codes from fcoe_rcv
drivers/scsi/fcoe/fcoe.c | 22 ++--
drivers/scsi/fcoe/fcoe_ctlr.c | 47 +++++---
drivers/scsi/fcoe/fcoe_sysfs.c | 12 +-
drivers/scsi/libfc/fc_exch.c | 251
++++++++++++++++++++++++++--------------
drivers/scsi/libfc/fc_fcp.c | 10 +-
drivers/scsi/libfc/fc_lport.c | 4 +-
drivers/scsi/libfc/fc_rport.c | 6 +-
include/scsi/fc/fc_fc2.h | 2 +-
include/scsi/libfc.h | 9 ++
9 files changed, 229 insertions(+), 134 deletions(-)
reply other threads:[~2013-09-05 19:12 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=5228D7AC.9050904@intel.com \
--to=robert.w.love@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).