From: "Love, Robert W" <robert.w.love@intel.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"fcoe-devel@open-fcoe.org" <fcoe-devel@open-fcoe.org>,
"Bhanu (Venkata Bhanu Prakash) Gollapudi" <bprakash@broadcom.com>
Subject: fcoe pull-request 3.9-rc5
Date: Mon, 1 Apr 2013 19:05:35 +0000 [thread overview]
Message-ID: <5159DA7E.7070606@intel.com> (raw)
The following changes since commit 8bb9660418e05bb1845ac1a2428444d78e322cc7:
Linux 3.9-rc4 (2013-03-23 16:52:44 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rwlove/fcoe.git
tags/for-3.9-rc
for you to fetch changes up to 0db0e377ab5be5d507a2fca3d78215cd2e83b974:
libfcoe: Fix fcoe_sysfs VN2VN mode (2013-03-25 16:04:22 -0700)
----------------------------------------------------------------
Critical patches to fix FCoE VN2VN mode with new interfaces targeting 3.9-rc
----------------------------------------------------------------
Robert Love (5):
bnx2fc: Make the fcoe_cltr the SCSI host parent
fcoe: Fix deadlock between create and destroy paths
libfc, fcoe, bnx2fc: Always use fcoe_disc_init for discovery
layer initialization
libfc, fcoe, bnx2fc: Split fc_disc_init into fc_disc_{init, config}
libfcoe: Fix fcoe_sysfs VN2VN mode
drivers/scsi/bnx2fc/bnx2fc_fcoe.c | 6 ++--
drivers/scsi/fcoe/fcoe.c | 15 +++++++---
drivers/scsi/fcoe/fcoe_ctlr.c | 60
++++++++++++++++++++++++++++---------
drivers/scsi/libfc/fc_disc.c | 26 +++++++++++-----
include/scsi/libfc.h | 3 +-
5 files changed, 80 insertions(+), 30 deletions(-)
reply other threads:[~2013-04-01 19:05 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=5159DA7E.7070606@intel.com \
--to=robert.w.love@intel.com \
--cc=bprakash@broadcom.com \
--cc=fcoe-devel@open-fcoe.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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).