From: "Love, Robert W" <robert.w.love@intel.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: fcoe pull-request - fixes for 3.11 merge window or RC
Date: Tue, 9 Jul 2013 19:48:27 +0000 [thread overview]
Message-ID: <51DC690A.8050303@intel.com> (raw)
The following changes since commit 8bb495e3f02401ee6f76d1b1d77f3ac9f079e376:
Linux 3.10 (2013-06-30 15:13:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rwlove/fcoe.git
tags/fixes_for_3.10
for you to fetch changes up to 7a5ed75a782a1f2de7fc773981ecd88bfa7595b1:
fcoe: Reduce number of sparse warnings (2013-07-09 11:19:00 -0700)
----------------------------------------------------------------
A short series of fixes to libfc, libfcoe and fcoe.
Most patches fix formatting problems, one changes
the behavior of which discovered ports can/will be
logged into and another fixes a memory leak.
----------------------------------------------------------------
Bart Van Assche (1):
fcoe: Reduce number of sparse warnings
Mark Rustad (2):
libfc: Reject PLOGI from nodes with incompatible role
fcoe: Stop fc_rport_priv structure leak
Neerav Parikh (1):
fcoe: Fix smatch warning in fcoe_fdmi_info function
Robert Love (3):
libfc: Remove extra space in fc_exch_timer_cancel definition
libfc: Differentiate echange timer cancellation debug statements
libfcoe: Fix meaningless log statement
Yi Zou (1):
fcoe: fix the link error status block sparse warnings
drivers/scsi/fcoe/fcoe.c | 26 +++++++++++++++-----------
drivers/scsi/fcoe/fcoe_ctlr.c | 4 ++++
drivers/scsi/fcoe/fcoe_sysfs.c | 24 ++++++++++++------------
drivers/scsi/fcoe/fcoe_transport.c | 28 ++++++----------------------
drivers/scsi/libfc/fc_exch.c | 4 ++--
drivers/scsi/libfc/fc_rport.c | 27 +++++++++++++++++++++++++++
6 files changed, 66 insertions(+), 47 deletions(-)
reply other threads:[~2013-07-09 19:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51DC690A.8050303@intel.com \
--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 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.