From: Robert Love <robert.w.love@intel.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 0/5] libfc, bnx2fc, fcoe fixes for 3.9-rc
Date: Mon, 25 Mar 2013 16:35:39 -0700 [thread overview]
Message-ID: <20130325233539.17257.76078.stgit@fritz> (raw)
This series fixes a few critical issues with FCoE in 3.9.
1) bnx2fc had incorrect scsi host linkage in sysfs which prevents fcoemon
(fcoe userspace daemon) from interacting with it correctly.
2) 3 patches fix VN2VN mode configuration with new FCoE control interfaces.
3) Fixed lockdep warning
These patches are needed to allow fcoe to move to the new sysfs interfaces.
I would like to see these pushed upstream for 3.9-rc. A pull-request mail
will immediately follow this series.
---
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(-)
--
Thanks, //Rob
next reply other threads:[~2013-03-25 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 23:35 Robert Love [this message]
2013-03-25 23:35 ` [PATCH 1/5] bnx2fc: Make the fcoe_cltr the SCSI host parent Robert Love
2013-03-25 23:35 ` [PATCH 2/5] fcoe: Fix deadlock between create and destroy paths Robert Love
2013-03-25 23:35 ` [PATCH 3/5] libfc, fcoe, bnx2fc: Always use fcoe_disc_init for discovery layer initialization Robert Love
2013-03-25 23:36 ` [PATCH 4/5] libfc, fcoe, bnx2fc: Split fc_disc_init into fc_disc_{init, config} Robert Love
2013-03-25 23:36 ` [PATCH 5/5] libfcoe: Fix fcoe_sysfs VN2VN mode Robert Love
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=20130325233539.17257.76078.stgit@fritz \
--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