From: Greg KH <gregkh@linuxfoundation.org>
To: Robert Love <robert.w.love@intel.com>
Cc: linux-scsi@vger.kernel.org, james.smart@emulex.com,
giridhar.malavali@qlogic.com
Subject: Re: [PATCH 0/4] FCoE Sysfs
Date: Mon, 12 Mar 2012 21:56:27 -0700 [thread overview]
Message-ID: <20120313045627.GA15426@kroah.com> (raw)
In-Reply-To: <20120312230915.10580.52548.stgit@localhost6.localdomain6>
On Mon, Mar 12, 2012 at 04:09:15PM -0700, Robert Love wrote:
> This patch series adds a sysfs layer to libfcoe. It adds
> a sysfs instance for FIP controllers (a SW entity) and
> discovered Fibre Channel Forwarders (FCFs), which are
> simply FCoE switches.
>
> The new sysfs code is used by any driver that currently
> uses libfcoe, namely fcoe.ko and bnx2fc_fcoe.ko. Any other
> FCoE capable device that wishes to use the high-level APIs
> defined in fcoe_syfs.h may, without having to use the
> the protocol processing portions of libfcoe.
>
> The code borrows heavily from the FC Transport, but is
> less complicated because it does not need to interact
> with the SCSI layer directly.
>
> I think one thing to consider with this series is that
> drivers, such as traditional HBAs, which wish to use
> this infrastructure will now need to depend on libfcoe.ko.
> It was either this or create a superfluous kernel module;
> I think libfcoe is an appropriate place for this code.
>
> This series was created against scsi-misc + 9 patches
> mailed by me to linux-scsi on 03/09/12. (Note that 10
> patches were mailed, but that patch 01/10 will be dropped)
>
> I'm not sure if there's somewhere I should cross-post
> this for general sysfs review. I don't think I'm doing
> anything odd; I added Greg K-H to the CC list to try and
> get some sysfs eyes on this code.
As you are adding new sysfs files, please always add the proper
Documentation/ABI/ files as well.
thanks,
greg k-h
prev parent reply other threads:[~2012-03-13 4:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 23:09 [PATCH 0/4] FCoE Sysfs Robert Love
2012-03-12 23:09 ` [PATCH 1/4] fcoe: Allocate fcoe_ctlr with fcoe_interface, not as a member Robert Love
2012-03-12 23:09 ` [PATCH 2/4] bnx2fc: Allocate fcoe_ctlr with bnx2fc_interface, " Robert Love
2012-03-12 23:09 ` [PATCH 3/4] libfcoe: Add fcoe_sysfs Robert Love
2012-03-13 5:00 ` Greg KH
2012-03-14 1:19 ` Love, Robert W
2012-03-14 2:42 ` Greg KH
2012-03-12 23:09 ` [PATCH 4/4] fcoe, bnx2fc, libfcoe: SW FCoE and bnx2fc use FCoE Syfs Robert Love
2012-03-13 4:56 ` Greg KH [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=20120313045627.GA15426@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=giridhar.malavali@qlogic.com \
--cc=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.org \
--cc=robert.w.love@intel.com \
/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.