From: Robert Love <robert.w.love@intel.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 0/6] libfc, libfcoe and fcoe patches for scsi-misc
Date: Fri, 20 Apr 2012 12:16:20 -0700 [thread overview]
Message-ID: <20120420191620.4634.94869.stgit@localhost6.localdomain6> (raw)
Here are a variety of fixes for the libfc, libfcoe and fcoe kernel
modules. I've included a pull request that points to a signed-tag.
I don't have many signatures on my pgp key as I haven't been to a
key signing party. It's up to you, James, as to whether you want
to use/trust it or not.
git://open-fcoe.org/fcoe/linux-fcoe.git tags/for-james-1
Thanks, //Rob
---
Dan Carpenter (1):
fcoe: remove a stray unlock
Robert Love (1):
fcoe: Don't hold rtnl_mutex in fcoe_update_src_mac
Vasu Dev (3):
fcoe: remove lport from net device before doing per cpu rx thread cleanup
libfc: flush lport worker after its disabled
libfc: defer releasing master lport until complete fcoe interface cleanuped up
Yi Zou (1):
libfcoe: fix VN2VN N_Port_ID Beacon source MAC
drivers/scsi/fcoe/fcoe.c | 41 ++++++++++++++++++++++++++++++-----------
drivers/scsi/fcoe/fcoe.h | 4 +++-
drivers/scsi/fcoe/fcoe_ctlr.c | 8 +++++++-
drivers/scsi/libfc/fc_lport.c | 2 +-
4 files changed, 41 insertions(+), 14 deletions(-)
--
next reply other threads:[~2012-04-20 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:16 Robert Love [this message]
2012-04-20 19:16 ` [PATCH 1/6] fcoe: remove lport from net device before doing per cpu rx thread cleanup Robert Love
2012-04-20 19:16 ` [PATCH 2/6] libfc: flush lport worker after its disabled Robert Love
2012-04-20 19:16 ` [PATCH 3/6] libfc: defer releasing master lport until complete fcoe interface cleanuped up Robert Love
2012-04-20 19:16 ` [PATCH 4/6] fcoe: Don't hold rtnl_mutex in fcoe_update_src_mac Robert Love
2012-05-10 7:53 ` James Bottomley
2012-04-20 19:16 ` [PATCH 5/6] libfcoe: fix VN2VN N_Port_ID Beacon source MAC Robert Love
2012-04-20 19:16 ` [PATCH 6/6] fcoe: remove a stray unlock 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=20120420191620.4634.94869.stgit@localhost6.localdomain6 \
--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).