From: James Smart <James.Smart@Emulex.Com>
To: Adrian Bunk <bunk@kernel.org>
Cc: James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] scsi/lpfc/: possible cleanups
Date: Wed, 14 Nov 2007 08:42:53 -0500 [thread overview]
Message-ID: <473AFB5D.5030303@emulex.com> (raw)
In-Reply-To: <20071105170733.GQ12045@stusta.de>
ACK
-- james s
Adrian Bunk wrote:
> This patch contains the following possible cleanups:
> - make the following needlessly global functions static:
> - lpfc_els.c: lpfc_register_new_vport()
> - lpfc_els.c: lpfc_issue_els_fdisc()
> - lpfc_els.c: lpfc_issue_fabric_iocb()
> - lpfc_els.c: lpfc_fabric_abort_vport()
> - lpfc_hbadisc.c: lpfc_dev_loss_tmo_handler()
> - lpfc_hbadisc.c: lpfc_mbx_cmpl_clear_la()
> - lpfc_hbadisc.c: lpfc_disc_flush_list()
> - lpfc_hbadisc.c: __lpfc_find_node()
> - lpfc_init.c: lpfc_hb_timeout()
> - lpfc_init.c: lpfc_block_mgmt_io()
> - lpfc_sli.c: __lpfc_sli_release_iocbq()
> - lpfc_sli.c: lpfc_sli_next_hbq_slot()
> - lpfc_sli.c: lpfc_sli_hbqbuf_init_hbqs()
> - lpfc_sli.c: lpfc_sli_hbqbuf_find()
> - lpfc_sli.c: __lpfc_sli_issue_iocb()
> - #if 0 the following unused global functions:
> - lpfc_els.c: lpfc_fabric_abort_flogi()
> - lpfc_hbadisc.c: lpfc_find_node()
> - lpfc_hbadisc.c: lpfc_findnode_rpi()
> - remove the unused exports
>
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
>
> ---
>
> drivers/scsi/lpfc/lpfc_crtn.h | 19 -------------------
> drivers/scsi/lpfc/lpfc_els.c | 18 ++++++++++++++----
> drivers/scsi/lpfc/lpfc_hbadisc.c | 13 +++++++++----
> drivers/scsi/lpfc/lpfc_init.c | 22 +++++++++++-----------
> drivers/scsi/lpfc/lpfc_sli.c | 10 +++++-----
> drivers/scsi/lpfc/lpfc_vport.c | 3 ---
> 6 files changed, 39 insertions(+), 46 deletions(-)
>
prev parent reply other threads:[~2007-11-14 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 17:07 [2.6 patch] scsi/lpfc/: possible cleanups Adrian Bunk
2007-11-14 13:42 ` James Smart [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=473AFB5D.5030303@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@SteelEye.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).