LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Anitha Chrisanthus <anitha.chrisanthus@intel.com>,
Sam Ravnborg <sam@ravnborg.org>,
edmund.j.dea@intel.com
Subject: Re: linux-next: build warning after merge of the kspp tree
Date: Mon, 30 Aug 2021 16:50:55 -0700 [thread overview]
Message-ID: <E98E0D1B-4865-4177-A98F-8274B699E25E@chromium.org> (raw)
In-Reply-To: <20210830184429.1ee4b4d8@canb.auug.org.au>
On August 30, 2021 1:44:29 AM PDT, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>Hi all,
>
>After merging the kspp tree, today's linux-next build (powerpc
>allyesconfig) produced this warning:
>
>drivers/gpu/drm/kmb/kmb_plane.c:135:20: warning: array subscript 3 is above array bounds of 'struct layer_status[1]' [-Warray-bounds]
> 135 | kmb->plane_status[plane_id].ctrl = LCD_CTRL_GL2_ENABLE;
> | ~~~~~~~~~~~~~~~~~^~~~~~~~~~
>In file included from drivers/gpu/drm/kmb/kmb_plane.c:17:
>drivers/gpu/drm/kmb/kmb_drv.h:48:23: note: while referencing 'plane_status'
> 48 | struct layer_status plane_status[KMB_MAX_PLANES];
> | ^~~~~~~~~~~~
Hi!
Ah yes, thanks for the report. I encountered this too, and have been told the warning will go away soon:
https://lore.kernel.org/lkml/BY5PR11MB4182ABD607EB99C1F68777928CC69@BY5PR11MB4182.namprd11.prod.outlook.com/
-Kees
next prev parent reply other threads:[~2021-08-30 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 8:44 Stephen Rothwell
2021-08-30 23:50 ` Kees Cook [this message]
2021-08-31 0:49 ` Stephen Rothwell
2021-09-06 5:41 ` Stephen Rothwell
2021-09-06 17:06 ` Kees Cook
2021-09-06 17:12 ` Linus Torvalds
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=E98E0D1B-4865-4177-A98F-8274B699E25E@chromium.org \
--to=keescook@chromium.org \
--cc=anitha.chrisanthus@intel.com \
--cc=edmund.j.dea@intel.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
--subject='Re: linux-next: build warning after merge of the kspp tree' \
/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
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).