From: James Smart <James.Smart@Emulex.Com>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/8] Rename 'state' attribute in lpfc and qla2xxx
Date: Fri, 21 Mar 2008 19:05:05 -0400 [thread overview]
Message-ID: <47E43F21.3000109@emulex.com> (raw)
In-Reply-To: <20080318133228.61EE225918@pentland.suse.de>
ACK.
-- james s
Hannes Reinecke wrote:
> lpfc and qla2xxx overwrite the standard 'state' attribute with
> custom callbacks. So rename the custom attributes to 'link_state'
> and retain the original meaning of the 'state' attribute.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
> drivers/scsi/lpfc/lpfc_attr.c | 10 +++++-----
> drivers/scsi/qla2xxx/qla_attr.c | 8 ++++----
> 2 files changed, 9 insertions(+), 9 deletions(-)
>
next prev parent reply other threads:[~2008-03-21 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 13:32 [PATCH 3/8] Rename 'state' attribute in lpfc and qla2xxx Hannes Reinecke
2008-03-21 23:05 ` James Smart [this message]
2008-03-25 3:53 ` Andrew Vasquez
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=47E43F21.3000109@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hare@suse.de \
--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