From: Robert Love <robert.w.love@intel.com>
To: James.Bottomley@HansenPartnership.com, linux-scsi@vger.kernel.org
Subject: [PATCH 0/3] Updated Open-FCoE patches for 2.6.31
Date: Wed, 10 Jun 2009 15:30:54 -0700 [thread overview]
Message-ID: <20090610223054.11663.26451.stgit@fritz> (raw)
The following series is an updated patchset for the libfc, libfcoe and fcoe runtime logging.
This is just a repost of previously posted patches. It is prepared against linux-next
because at the time of this posting linux-next has scsi-misc and net-next merged.
---
Robert Love (3):
libfc: Add runtime debugging with debug_logging module parameter
libfcoe: Add runtime debugging with module param debug_logging
fcoe: Add runtime debug logging with module parameter debug_logging
drivers/scsi/fcoe/fcoe.c | 108 ++++++++++++++--------------
drivers/scsi/fcoe/fcoe.h | 24 ++++++
drivers/scsi/fcoe/libfcoe.c | 94 ++++++++++++++-----------
drivers/scsi/libfc/fc_disc.c | 83 +++++++++-------------
drivers/scsi/libfc/fc_exch.c | 58 +++++++--------
drivers/scsi/libfc/fc_fcp.c | 97 +++++++++++++------------
drivers/scsi/libfc/fc_lport.c | 156 ++++++++++++++++++++---------------------
drivers/scsi/libfc/fc_rport.c | 120 +++++++++++++-------------------
include/scsi/fc_encode.h | 2 -
include/scsi/libfc.h | 77 +++++++++++++++++---
10 files changed, 432 insertions(+), 387 deletions(-)
--
//Rob
next reply other threads:[~2009-06-10 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 22:30 Robert Love [this message]
2009-06-10 22:30 ` [PATCH 1/3] fcoe: Add runtime debug logging with module parameter debug_logging Robert Love
2009-06-10 22:31 ` [PATCH 2/3] libfcoe: Add runtime debugging with module param debug_logging Robert Love
2009-06-10 22:31 ` [PATCH 3/3] libfc: Add runtime debugging with debug_logging module parameter 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=20090610223054.11663.26451.stgit@fritz \
--to=robert.w.love@intel.com \
--cc=James.Bottomley@HansenPartnership.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.