From: Marek Vasut <marex@denx.de>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Stefan Agner <stefan@agner.ch>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] drm: mxsfb: Fix NULL pointer dereference
Date: Wed, 2 Feb 2022 09:30:38 +0100 [thread overview]
Message-ID: <61ec1e37-d1a2-6561-493a-06bf37cd71d6@denx.de> (raw)
In-Reply-To: <20220202081755.145716-3-alexander.stein@ew.tq-group.com>
On 2/2/22 09:17, Alexander Stein wrote:
> mxsfb should not never dereference the NULL pointer which
... not ever ... but that's really a nitpick.
> drm_atomic_get_new_bridge_state is allowed to return.
> Assume a fixed format instead.
>
> Fixes: commit b776b0f00f24 ("drm: mxsfb: Use bus_format from the nearest bridge if present")
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
It's perfect otherwise, thanks !
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-02 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 8:17 [PATCH v2 0/2] mxsfb fixes Alexander Stein
2022-02-02 8:17 ` [PATCH v2 1/2] drm: mxsfb: Use dev_err_probe() helper Alexander Stein
2022-02-02 8:29 ` Marek Vasut
2022-02-02 8:58 ` (EXT) " Alexander Stein
2022-02-02 9:03 ` Marek Vasut
2022-02-03 8:58 ` Marek Vasut
2022-02-02 8:17 ` [PATCH v2 2/2] drm: mxsfb: Fix NULL pointer dereference Alexander Stein
2022-02-02 8:30 ` Marek Vasut [this message]
2022-02-02 9:00 ` (EXT) " Alexander Stein
2022-02-02 9:03 ` Marek Vasut
2022-02-03 8:58 ` Marek Vasut
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=61ec1e37-d1a2-6561-493a-06bf37cd71d6@denx.de \
--to=marex@denx.de \
--cc=airlied@linux.ie \
--cc=alexander.stein@ew.tq-group.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).