netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] defxx: fix build warning
Date: Mon, 25 Jan 2016 07:07:54 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1601250654160.7055@eddie.linux-mips.org> (raw)
In-Reply-To: <1453702507-736-1-git-send-email-sudipm.mukherjee@gmail.com>

On Mon, 25 Jan 2016, Sudip Mukherjee wrote:

> We are getting many build warning about:
> 'bar_start' may be used uninitialized
> and
> 'bar_len' may be used uninitialized
> 
> They are not actually uninitialized as dfx_get_bars() will initialize
> them properly. But still lets have them initialized just to satisfy the
> compiler.

 Which compiler/version is that?

> diff --git a/drivers/net/fddi/defxx.c b/drivers/net/fddi/defxx.c
> index 7f975a2..4113535 100644
> --- a/drivers/net/fddi/defxx.c
> +++ b/drivers/net/fddi/defxx.c
> @@ -533,8 +533,8 @@ static int dfx_register(struct device *bdev)
>  	const char *print_name = dev_name(bdev);
>  	struct net_device *dev;
>  	DFX_board_t	  *bp;			/* board pointer */
> -	resource_size_t bar_start[3];		/* pointers to ports */
> -	resource_size_t bar_len[3];		/* resource length */
> +	resource_size_t bar_start[3] = {0, 0, 0};	/* pointers to ports */
> +	resource_size_t bar_len[3] = {0, 0, 0};		/* resource length */
>  	int alloc_size;				/* total buffer size used */
>  	struct resource *region;
>  	int err = 0;

 Just setting the first element will do, the rest will then be implicitly 
zeroed, following the semantics of initialisers in C.  So just do:

	resource_size_t bar_start[3] = {0};	/* pointers to ports */
	resource_size_t bar_len[3] = {0};	/* resource length */

for brevity and to save formatting.

> @@ -3697,8 +3697,8 @@ static void dfx_unregister(struct device *bdev)
>  	int dfx_bus_pci = dev_is_pci(bdev);
>  	int dfx_bus_tc = DFX_BUS_TC(bdev);
>  	int dfx_use_mmio = DFX_MMIO || dfx_bus_tc;
> -	resource_size_t bar_start[3];		/* pointers to ports */
> -	resource_size_t bar_len[3];		/* resource lengths */
> +	resource_size_t bar_start[3] = {0, 0, 0};	/* pointers to ports */
> +	resource_size_t bar_len[3] = {0, 0, 0};		/* resource lengths */
>  	int		alloc_size;		/* total buffer size used */
>  
>  	unregister_netdev(dev);

 Likewise here.  Please resend with the update requested and I'll ack it.

 Thanks for your submission!

  Maciej

      reply	other threads:[~2016-01-25  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  6:15 [PATCH 3/3] defxx: fix build warning Sudip Mukherjee
2016-01-25  7:07 ` Maciej W. Rozycki [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=alpine.LFD.2.20.1601250654160.7055@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    /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).