From: "Love, Robert W" <robert.w.love@intel.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"giridhar.malavali@qlogic.com" <giridhar.malavali@qlogic.com>,
"james.smart@emulex.com" <james.smart@emulex.com>,
"bprakash@broadcom.com" <bprakash@broadcom.com>
Subject: Re: [PATCH v4 0/4] FCoE Sysfs
Date: Tue, 15 May 2012 17:40:24 +0000 [thread overview]
Message-ID: <4FB29507.2060104@intel.com> (raw)
In-Reply-To: <20120327222224.7144.6324.stgit@localhost6.localdomain6>
On 03/27/2012 03:22 PM, Robert Love wrote:
> v4: Minor fixes and cleanups
>
> * Changed device_initialize/device_add to device_register
> and device_del to device_unregister. There was an imbalance
> because device_initialize was getting a reference that
> was not being released. With this update both fcoe_fcfs
> as well as fcoe_ctlrs are correctly released/free'd when
> they are to be removed from the system.
>
> * Minor updates to commit messages so there are no
> references to 'fcoe_ctlr_attrs' and 'fcoe_fcf_attrs'
> which were both renamed in v3 of this series.
Hi James,
Any thoughts on whether this series will make it for the upcoming
merge window? Greg KH Ack-ed it about two months ago and my impression
was that everyone agreed to the change at LSF a month ago. What do you
think?
//Rob
next prev parent reply other threads:[~2012-05-15 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 22:22 [PATCH v4 0/4] FCoE Sysfs Robert Love
2012-03-27 22:22 ` [PATCH v4 1/4] fcoe: Allocate fcoe_ctlr with fcoe_interface, not as a member Robert Love
2012-05-22 21:01 ` James Bottomley
2012-03-27 22:22 ` [PATCH v4 2/4] bnx2fc: Allocate fcoe_ctlr with bnx2fc_interface, " Robert Love
2012-03-27 22:22 ` [PATCH v4 3/4] libfcoe: Add fcoe_sysfs Robert Love
2012-03-27 22:22 ` [PATCH v4 4/4] fcoe, bnx2fc, libfcoe: SW FCoE and bnx2fc use FCoE Syfs Robert Love
2012-05-15 17:40 ` Love, Robert W [this message]
2012-05-15 17:47 ` [PATCH v4 0/4] FCoE Sysfs gregkh
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=4FB29507.2060104@intel.com \
--to=robert.w.love@intel.com \
--cc=bprakash@broadcom.com \
--cc=giridhar.malavali@qlogic.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.smart@emulex.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.