From: Shan Wei <shanwei@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net:bna: fix compile warning of ‘bfa_ioc_smem_pgoff’ defined but not used
Date: Wed, 20 Apr 2011 09:42:30 +0800 [thread overview]
Message-ID: <4DAE3A06.4000207@cn.fujitsu.com> (raw)
In-Reply-To: <4DAE38FE.1010503@cn.fujitsu.com>
This patch is also against net-next.
Shan Wei wrote, at 04/20/2011 09:38 AM:
> Fix the below compile warning:
>
> drivers/net/bna/bfa_ioc.c:1922: warning: ‘bfa_ioc_smem_pgoff’ defined but not used
>
>
> Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
> ---
> drivers/net/bna/bfa_ioc.c | 7 -------
> 1 files changed, 0 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/bna/bfa_ioc.c b/drivers/net/bna/bfa_ioc.c
> index ba2a4e1..fcb9bb3 100644
> --- a/drivers/net/bna/bfa_ioc.c
> +++ b/drivers/net/bna/bfa_ioc.c
> @@ -82,7 +82,6 @@ static void bfa_ioc_pf_fwmismatch(struct bfa_ioc *ioc);
> static void bfa_ioc_boot(struct bfa_ioc *ioc, u32 boot_type,
> u32 boot_param);
> static u32 bfa_ioc_smem_pgnum(struct bfa_ioc *ioc, u32 fmaddr);
> -static u32 bfa_ioc_smem_pgoff(struct bfa_ioc *ioc, u32 fmaddr);
> static void bfa_ioc_get_adapter_serial_num(struct bfa_ioc *ioc,
> char *serial_num);
> static void bfa_ioc_get_adapter_fw_ver(struct bfa_ioc *ioc,
> @@ -1923,12 +1922,6 @@ bfa_ioc_smem_pgnum(struct bfa_ioc *ioc, u32 fmaddr)
> return PSS_SMEM_PGNUM(ioc->ioc_regs.smem_pg0, fmaddr);
> }
>
> -static u32
> -bfa_ioc_smem_pgoff(struct bfa_ioc *ioc, u32 fmaddr)
> -{
> - return PSS_SMEM_PGOFF(fmaddr);
> -}
> -
> /**
> * Register mailbox message handler function, to be called by common modules
> */
--
Best Regards
-----
Shan Wei
next prev parent reply other threads:[~2011-04-20 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 1:38 [PATCH] net:bna: fix compile warning of ‘bfa_ioc_smem_pgoff’ defined but not used Shan Wei
2011-04-20 1:42 ` Shan Wei [this message]
2011-04-20 3:12 ` David Miller
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=4DAE3A06.4000207@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=davem@davemloft.net \
--cc=netdev@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).