public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Kashyap, Desai" <kashyap.desai@lsi.com>
Cc: linux-scsi@vger.kernel.org, Eric.Moore@lsi.com, Sathya.Prakash@lsi.com
Subject: Re: [PATCH 14/24] mpt fusion: [2.6.30-rc6] Deleted functions for Firmware event implementation using seperate WQ
Date: Wed, 27 May 2009 17:33:53 +0000	[thread overview]
Message-ID: <1243445633.6067.31.camel@localhost.localdomain> (raw)
In-Reply-To: <20090522110447.GH16331@lsi.com>

On Fri, 2009-05-22 at 16:34 +0530, Kashyap, Desai wrote:
> Fuctions which are not used are removed by this patch.
> ---
> 
> Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
> ---
> diff --git a/drivers/message/fusion/mptsas.c b/drivers/message/fusion/mptsas.c
> index 10abd62..29a8fe2 100644
> --- a/drivers/message/fusion/mptsas.c
> +++ b/drivers/message/fusion/mptsas.c
> @@ -3035,30 +3035,6 @@ mptsas_find_phyinfo_by_sas_address(MPT_ADAPTER *ioc, u64 sas_address)
>  	return phy_info;
>  }
>  
> -static struct mptsas_phyinfo *
> -mptsas_find_phyinfo_by_target(MPT_ADAPTER *ioc, u8 channel, u8 id)

Please combine this with the patch that actually removes the last use
otherwise, for all static functions, gcc is going to warn about defined
but unused functions.

The 10 lines you save by separating this aren't really significant given
that some of the other patches are up to a thousand lines.

James



      reply	other threads:[~2009-05-27 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 11:04 [PATCH 14/24] mpt fusion: [2.6.30-rc6] Deleted functions for Firmware event implementation using seperate WQ Kashyap, Desai
2009-05-27 17:33 ` James Bottomley [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=1243445633.6067.31.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Eric.Moore@lsi.com \
    --cc=Sathya.Prakash@lsi.com \
    --cc=kashyap.desai@lsi.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