From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] Fix gcc4 error incomplete array element type
Date: Fri, 20 May 2005 05:09:22 +0000 [thread overview]
Message-ID: <20050520050922.GA10292@kroah.com> (raw)
In-Reply-To: <428D6C84.8070708@cs.pdx.edu>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Thu, May 19, 2005 at 09:50:12PM -0700, Jesse Millan wrote:
> This patch is in regards to fixing the gcc 4 warnings. It actually fixes
> a gcc 4 error by changing
>
> struct i2c_msg msg[]
>
> to
>
> struct i2c_msg *msg
>
> which is what gcc4 wants to see from now on.
>
> F.Y.I I applied the kj patch, and this error has not been fixed as of
> yet. However, I found that this was changed in Andrew Morton mm4 patch.
This is already fixed in the 2.6.12-rc4 kernel, correct?
thanks,
greg k-h
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-05-20 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 4:50 [KJ] [PATCH] Fix gcc4 error incomplete array element type Jesse Millan
2005-05-20 5:09 ` Greg KH [this message]
2005-05-20 5:10 ` Greg KH
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=20050520050922.GA10292@kroah.com \
--to=greg@kroah.com \
--cc=kernel-janitors@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).