From: Sam Ravnborg <sam@ravnborg.org>
To: "Chrisanthus, Anitha" <anitha.chrisanthus@intel.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
"Dea, Edmund J" <edmund.j.dea@intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>, lkp <lkp@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/kmb: fix array bounds warning
Date: Sat, 5 Dec 2020 20:59:35 +0100 [thread overview]
Message-ID: <20201205195935.GJ332836@ravnborg.org> (raw)
In-Reply-To: <BY5PR11MB4182B94E480EFACBF817DFFF8CF50@BY5PR11MB4182.namprd11.prod.outlook.com>
Hi Anitha,
On Mon, Nov 30, 2020 at 10:19:13PM +0000, Chrisanthus, Anitha wrote:
> Hi Arnd,
> Thanks for your patch.
>
> > -----Original Message-----
> > From: Arnd Bergmann <arnd@kernel.org>
> > Sent: Sunday, November 29, 2020 12:09 PM
> > To: Chrisanthus, Anitha <anitha.chrisanthus@intel.com>; Dea, Edmund J
> > <edmund.j.dea@intel.com>; David Airlie <airlied@linux.ie>; Daniel Vetter
> > <daniel@ffwll.ch>; Sam Ravnborg <sam@ravnborg.org>
> > Cc: Arnd Bergmann <arnd@arndb.de>; lkp <lkp@intel.com>; dri-
> > devel@lists.freedesktop.org; linux-kernel@vger.kernel.org
> > Subject: [PATCH] drm/kmb: fix array bounds warning
> >
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > gcc warns about an out-of-bounds access when the using nonzero
> > values for 'plane_id' on kmb->plane_status:
...
> Looks good.
>
> Reviewed-by: Anitha Chrisanthus <anitha.chrisanthus@intel.com>
You wanted a little time to get comforable with dim, so I picked up this
patch and pushed it to drm-misc-next.
Sam
prev parent reply other threads:[~2020-12-05 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 20:09 [PATCH] drm/kmb: fix array bounds warning Arnd Bergmann
2020-11-30 22:19 ` Chrisanthus, Anitha
2020-12-05 19:59 ` Sam Ravnborg [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=20201205195935.GJ332836@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=anitha.chrisanthus@intel.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=edmund.j.dea@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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