linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Love, Robert W" <robert.w.love@intel.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: FCoE Updates for 3.8
Date: Fri, 14 Dec 2012 22:33:19 +0000	[thread overview]
Message-ID: <50CBA92E.6090607@intel.com> (raw)
In-Reply-To: <20121213004550.GA19743@fritz.jf.intel.com>

On Wed 12 Dec 2012 04:45:50 PM PST, Robert Love wrote:
> The following changes since commit b69f0859dc8e633c5d8c06845811588fe17e68b3:
>
>    Linux 3.7-rc8 (2012-12-03 11:22:37 -0800)
>
> are available in the git repository at:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/rwlove/fcoe.git for-next-12-12-12
>
> for you to fetch changes up to 04f0ac991b5dd2a32c3fa3dcb2cf34830949afa5:
>
>    debris left by "[SCSI] libfcoe: Remove mutex_trylock/restart_syscall checks" (2012-12-11 10:22:36 -0800)
>
> ----------------------------------------------------------------
> Al Viro (1):
>        debris left by "[SCSI] libfcoe: Remove mutex_trylock/restart_syscall checks"
>
> Robert Love (7):
>        Documentation: Add missing devices/ to devices path
>        libfcoe: Save some memory and optimize name lookups
>        libfcoe: Add fcoe_sysfs debug logging level
>        libfcoe, fcoe, bnx2fc: Add new fcoe control interface
>        fcoe: Use the fcoe_sysfs control interface
>        bnx2fc: Use the fcoe_sysfs control interface
>        libfc, libfcoe, fcoe: Convert debug_logging macros to pr_info
>
> Vasu Dev (1):
>        libfc: fix REC handling
>
> Yi Zou (7):
>        fcoe: prep work to start consolidate the usage of fcoe_netdev
>        fcoe: add support to the get_netdev() for fcoe_interface
>        libfcoe, fcoe: move fcoe_link_speed_update() to libfcoe and export it
>        libfcoe, fcoe: consolidate the fcoe_ctlr_get_lesb/fcoe_get_lesb
>        bnx2fc: add support to get_netdev for bnx2f_interface
>        bnx2fc: use fcoe_link_speed_update() from the exported symbol in libfcoe
>        bnx2fc: use fcoe_get_lesb/fcoe_ctlr_get_lesb() directly from libfcoe
>
>   Documentation/ABI/testing/sysfs-bus-fcoe |   45 +++++-
>   drivers/scsi/bnx2fc/bnx2fc_fcoe.c        |  256 +++++++++++++++++-------------
>   drivers/scsi/fcoe/fcoe.c                 |  212 +++++++++++++++----------
>   drivers/scsi/fcoe/fcoe.h                 |    6 +-
>   drivers/scsi/fcoe/fcoe_ctlr.c            |   17 +-
>   drivers/scsi/fcoe/fcoe_sysfs.c           |  186 ++++++++++++++++++----
>   drivers/scsi/fcoe/fcoe_transport.c       |  199 ++++++++++++++++++++++-
>   drivers/scsi/fcoe/libfcoe.h              |   20 ++-
>   drivers/scsi/libfc/fc_fcp.c              |    6 +-
>   drivers/scsi/libfc/fc_libfc.h            |   38 ++---
>   include/scsi/fcoe_sysfs.h                |   11 +-
>   include/scsi/libfcoe.h                   |   32 +++-
>   12 files changed, 749 insertions(+), 279 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Please ignore this request. A new (v2) pull request is coming that 
addresses Bart's feedback on one patch.

Thanks, //Rob


      reply	other threads:[~2012-12-14 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13  0:45 FCoE Updates for 3.8 Robert Love
2012-12-14 22:33 ` Love, Robert W [this message]

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=50CBA92E.6090607@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 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).