From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
Pin-Yen Lin <treapking@chromium.org>
Cc: Tzung-Bi Shih <tzungbi@google.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Pin-Yen Lin <treapking@chromium.org>,
Maxime Ripard <maxime@cerno.tech>,
Pi-Hsun Shih <pihsun@chromium.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Sam Ravnborg <sam@ravnborg.org>, Xin Ji <xji@analogixsemi.com>
Subject: Re: [PATCH] drm/bridge: anx7625: Fix overflow issue on reading EDID
Date: Wed, 09 Feb 2022 18:28:14 +0100 [thread overview]
Message-ID: <3151389.aeNJFYEL58@kista> (raw)
In-Reply-To: <20220209055327.2472561-1-treapking@chromium.org>
Hi!
Dne sreda, 09. februar 2022 ob 06:53:27 CET je Pin-Yen Lin napisal(a):
> The length of EDID block can be longer than 256 bytes, so we should use
> `int` instead of `u8` for the `edid_pos` variable.
>
> Signed-off-by: Pin-Yen Lin <treapking@chromium.org>
Please add "Fixes" tag. With that:
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
WARNING: multiple messages have this Message-ID (diff)
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
Pin-Yen Lin <treapking@chromium.org>
Cc: Pin-Yen Lin <treapking@chromium.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Maxime Ripard <maxime@cerno.tech>,
Pi-Hsun Shih <pihsun@chromium.org>,
Sam Ravnborg <sam@ravnborg.org>,
Tzung-Bi Shih <tzungbi@google.com>, Xin Ji <xji@analogixsemi.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/bridge: anx7625: Fix overflow issue on reading EDID
Date: Wed, 09 Feb 2022 18:28:14 +0100 [thread overview]
Message-ID: <3151389.aeNJFYEL58@kista> (raw)
In-Reply-To: <20220209055327.2472561-1-treapking@chromium.org>
Hi!
Dne sreda, 09. februar 2022 ob 06:53:27 CET je Pin-Yen Lin napisal(a):
> The length of EDID block can be longer than 256 bytes, so we should use
> `int` instead of `u8` for the `edid_pos` variable.
>
> Signed-off-by: Pin-Yen Lin <treapking@chromium.org>
Please add "Fixes" tag. With that:
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
next prev parent reply other threads:[~2022-02-09 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 5:53 [PATCH] drm/bridge: anx7625: Fix overflow issue on reading EDID Pin-Yen Lin
2022-02-09 5:53 ` Pin-Yen Lin
2022-02-09 17:28 ` Jernej Škrabec [this message]
2022-02-09 17:28 ` Jernej Škrabec
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=3151389.aeNJFYEL58@kista \
--to=jernej.skrabec@gmail.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hsinyi@chromium.org \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=narmstrong@baylibre.com \
--cc=pihsun@chromium.org \
--cc=robert.foss@linaro.org \
--cc=sam@ravnborg.org \
--cc=treapking@chromium.org \
--cc=tzungbi@google.com \
--cc=xji@analogixsemi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.