From: "Maxime Ripard" <mripard@kernel.org>
To: "Javier Martinez Canillas" <javierm@redhat.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH v4] drm/ssd130x: Allocate buffers in the plane's .atomic_check callback
Date: Fri, 21 Jul 2023 07:33:42 +0000 [thread overview]
Message-ID: <c3169a54ab922cfefd4372ce897446ba.mripard@kernel.org> (raw)
In-Reply-To: <20230721070955.1170974-1-javierm@redhat.com>
On Fri, 21 Jul 2023 09:09:50 +0200, Javier Martinez Canillas wrote:
> Geert reports that the following NULL pointer dereference happens for him
> after commit 49d7d581ceaf ("drm/ssd130x: Don't allocate buffers on each
> plane update"):
>
> [drm] Initialized ssd130x 1.0.0 20220131 for 0-003c on minor 0
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2023-07-21 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 7:09 Javier Martinez Canillas
2023-07-21 7:33 ` Maxime Ripard [this message]
2023-07-25 19:21 ` Geert Uytterhoeven
2023-07-25 20:49 ` Javier Martinez Canillas
2023-07-26 9:59 ` Maxime Ripard
2023-07-26 10:39 ` Javier Martinez Canillas
2023-07-26 11:52 ` Geert Uytterhoeven
2023-07-26 12:22 ` Javier Martinez Canillas
2023-07-26 12:33 ` Geert Uytterhoeven
2023-07-26 13:54 ` Maxime Ripard
2023-07-26 14:14 ` Geert Uytterhoeven
2023-07-26 14:22 ` Javier Martinez Canillas
2023-07-26 13:49 ` Maxime Ripard
2023-07-26 14:16 ` Javier Martinez Canillas
2023-07-27 12:52 ` Thomas Zimmermann
2023-07-27 13:43 ` Javier Martinez Canillas
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=c3169a54ab922cfefd4372ce897446ba.mripard@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®