public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: John Cherry <cherry@osdl.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Gerd Knorr <kraxel@bytesex.org>
Subject: Re: IA32 (2.6.11 - 2005-03-12.16.00) - 56 New warnings
Date: Sun, 13 Mar 2005 13:43:34 +0100	[thread overview]
Message-ID: <20050313124333.GA26569@linuxtv.org> (raw)
In-Reply-To: <200503130508.j2D58jTQ014587@ibm-f.pdx.osdl.net>

On Sat, Mar 12, 2005 at 09:08:45PM -0800, John Cherry wrote:
> drivers/media/dvb/frontends/dvb-pll.c:104: warning: (near initialization for `dvb_pll_unknown_1.entries')
> drivers/media/dvb/frontends/dvb-pll.c:104: warning: excess elements in array initializer
> drivers/media/dvb/frontends/dvb-pll.c:105: warning: (near initialization for `dvb_pll_unknown_1.entries')
> drivers/media/dvb/frontends/dvb-pll.c:105: warning: excess elements in array initializer
[snip]

Gerd's original patch had

	struct dvb_pll_desc {
		char *name;
		u32  min;
		u32  max;
		void (*setbw)(u8 *buf, int bandwidth);
		int  count;
		struct {
			u32 limit;
			u32 offset;
			u32 stepsize;
			u8  cb1;
			u8  cb2;
		} entries[];
	};

while 2.6.11-mm3 changed it into entries[0]. I assume this was made
for gcc-4.0 compatibility? But the element type for entries is
fully defined, so it should not be a problem (as long as no one tries to
created arrays of struct dvb_pll_desc)?

Johannes

  reply	other threads:[~2005-03-13 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-13  5:08 IA32 (2.6.11 - 2005-03-12.16.00) - 56 New warnings John Cherry
2005-03-13 12:43 ` Johannes Stezenbach [this message]
2005-03-13 19:35   ` Andrew Morton
2005-03-14  9:41     ` Gerd Knorr

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=20050313124333.GA26569@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=akpm@osdl.org \
    --cc=cherry@osdl.org \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@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