From: Robert Love <robert.w.love@intel.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 0/4] libfc, libfcoe, fcoe updates for 3.10-rc
Date: Tue, 21 May 2013 10:44:26 -0700 [thread overview]
Message-ID: <20130521174426.3033.16298.stgit@fritz> (raw)
The following series implements a few random fixes.
---
Krishna Mohan (1):
libfcoe: Fix Conflicting FCFs issue in the fabric
Mark Rustad (1):
libfc: Correct check for initiator role
Neil Horman (2):
libfc: extend ex_lock to protect all of fc_seq_send
MAINTAINERS: Fix fcoe mailing list
MAINTAINERS | 2 +-
drivers/scsi/fcoe/fcoe_ctlr.c | 15 +++++----------
drivers/scsi/libfc/fc_exch.c | 37 ++++++++++++++++++++++++-------------
drivers/scsi/libfc/fc_rport.c | 2 +-
4 files changed, 31 insertions(+), 25 deletions(-)
--
Thanks, //Rob
next reply other threads:[~2013-05-21 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 17:44 Robert Love [this message]
2013-05-21 17:44 ` [PATCH 1/4] libfcoe: Fix Conflicting FCFs issue in the fabric Robert Love
2013-05-21 17:44 ` [PATCH 2/4] libfc: Correct check for initiator role Robert Love
2013-05-21 17:44 ` [PATCH 3/4] libfc: extend ex_lock to protect all of fc_seq_send Robert Love
2013-05-21 17:44 ` [PATCH 4/4] MAINTAINERS: Fix fcoe mailing list 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=20130521174426.3033.16298.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