public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <robert.w.love@intel.com>
To: James.Bottomley@suse.de, linux-scsi@vger.kernel.org
Subject: [PATCH 0/5] libfc/libfcoe/fcoe fixes for 2.6.33-rc
Date: Thu, 21 Jan 2010 10:15:39 -0800	[thread overview]
Message-ID: <20100121181538.16741.33676.stgit@localhost.localdomain> (raw)

The following series implements a few fixes to libfc, libfcoe and fcoe.

---

Bhanu Prakash Gollapudi (1):
      libfcoe: Send port LKA every FIP_VN_KA_PERIOD secs.

Hugh Daschbach (2):
      libfc: Don't assume response request present.
      libfc: Fix e_d_tov ns -> ms scaling factor in PLOGI response.

Rob Love (1):
      fcoe: Only rmmod fcoe.ko if there are no active connections

Vasu Dev (1):
      libfc: call ddp setup for only FCP reads to avoid accessing junk fsp pointer


 drivers/scsi/fcoe/fcoe.c      |   18 ++++++++++++++++--
 drivers/scsi/fcoe/libfcoe.c   |    2 +-
 drivers/scsi/libfc/fc_exch.c  |    2 +-
 drivers/scsi/libfc/fc_fcp.c   |    3 ---
 drivers/scsi/libfc/fc_lport.c |    3 ++-
 drivers/scsi/libfc/fc_rport.c |    2 +-
 6 files changed, 21 insertions(+), 9 deletions(-)

-- 
//Rob

             reply	other threads:[~2010-01-21 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 18:15 Robert Love [this message]
2010-01-21 18:15 ` [PATCH 1/5] libfc: call ddp setup for only FCP reads to avoid accessing junk fsp pointer Robert Love
2010-01-21 18:15 ` [PATCH 2/5] libfc: Fix e_d_tov ns -> ms scaling factor in PLOGI response Robert Love
2010-01-21 18:15 ` [PATCH 3/5] libfc: Don't assume response request present Robert Love
2010-01-21 18:16 ` [PATCH 4/5] libfcoe: Send port LKA every FIP_VN_KA_PERIOD secs Robert Love
2010-01-21 18:16 ` [PATCH 5/5] fcoe: Only rmmod fcoe.ko if there are no active connections 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=20100121181538.16741.33676.stgit@localhost.localdomain \
    --to=robert.w.love@intel.com \
    --cc=James.Bottomley@suse.de \
    --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