From: David Miller <davem@davemloft.net>
To: danny.kukawka@bisect.de
Cc: mac@melware.de, dkukawka@suse.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, isdn@linux-pingi.de,
bhutchings@solarflare.com, David.Laight@aculab.com
Subject: Re: [PATCH v2] eicon: fix -Warray-bounds warning
Date: Thu, 02 Feb 2012 14:50:36 -0500 (EST) [thread overview]
Message-ID: <20120202.145036.1235867786947627132.davem@davemloft.net> (raw)
In-Reply-To: <1328188830-28133-1-git-send-email-danny.kukawka@bisect.de>
From: Danny Kukawka <danny.kukawka@bisect.de>
Date: Thu, 2 Feb 2012 14:20:28 +0100
> Fix for a -Warray-bounds warning. mixer_notify_update() tries to
> write to ((CAPI_MSG *) msg)->info.facility_req.structs[3] while
> structs is defined as byte structs[1]. Set all 'structs' which are
> part of the typdefs in the info union to 'byte structs[0]'.
>
> v2: set all info.*.structs to byte structs[0]
>
> Signed-off-by: Danny Kukawka <danny.kukawka@bisect.de>
Applied, thanks.
prev parent reply other threads:[~2012-02-02 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 13:20 [PATCH v2] eicon: fix -Warray-bounds warning Danny Kukawka
2012-02-02 19:50 ` David Miller [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=20120202.145036.1235867786947627132.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@aculab.com \
--cc=bhutchings@solarflare.com \
--cc=danny.kukawka@bisect.de \
--cc=dkukawka@suse.de \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mac@melware.de \
--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).