From: Robert Foss <robert.foss@linaro.org>
To: andrzej.hajda@intel.com, narmstrong@baylibre.com,
robert.foss@linaro.org, Laurent.pinchart@ideasonboard.com,
jonas@kwiboo.se, jernej.skrabec@gmail.com, airlied@linux.ie,
daniel@ffwll.ch, dianders@chromium.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Chris Morgan <macromorgan@hotmail.com>,
devicetree@vger.kernel.org
Subject: [PATCH v2 0/2] Fix chrontel-ch7033 reversion
Date: Mon, 19 Sep 2022 12:20:07 +0200 [thread overview]
Message-ID: <20220919102009.150503-1-robert.foss@linaro.org> (raw)
When the chrontel-ch7033 series from Chris Morgan was reverted[1], I made mistake.
Patch 2/2 in this[1] series reverts [2] when it should have reverted [3].
This series fixes this mistake.
[1] https://lore.kernel.org/all/20220912113856.817188-1-robert.foss@linaro.org/
[2] c312b0df3b13 - drm/bridge: ti-sn65dsi86: Implement bridge connector operations for DP
[3] ce9564cfc9ae - drm/bridge: chrontel-ch7033: Add byteswap order setting
Changes since v1:
- Add Fixes tag (Laurent)
Robert Foss (2):
Revert "Revert "drm/bridge: ti-sn65dsi86: Implement bridge connector
operations for DP""
Revert "drm/bridge: chrontel-ch7033: Add byteswap order setting"
drivers/gpu/drm/bridge/chrontel-ch7033.c | 15 ++-----------
drivers/gpu/drm/bridge/ti-sn65dsi86.c | 28 ++++++++++++++++++++++++
2 files changed, 30 insertions(+), 13 deletions(-)
--
2.34.1
next reply other threads:[~2022-09-19 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 10:20 Robert Foss [this message]
2022-09-19 10:20 ` [PATCH v2 1/2] Revert "Revert "drm/bridge: ti-sn65dsi86: Implement bridge connector operations for DP"" Robert Foss
2022-09-19 10:43 ` Laurent Pinchart
2022-09-19 10:43 ` Laurent Pinchart
2022-09-19 10:20 ` [PATCH v2 2/2] Revert "drm/bridge: chrontel-ch7033: Add byteswap order setting" Robert Foss
2022-09-19 10:47 ` Laurent Pinchart
2022-09-19 10:47 ` Laurent Pinchart
2022-09-19 13:18 ` Robert Foss
2022-09-19 13:18 ` Robert Foss
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=20220919102009.150503-1-robert.foss@linaro.org \
--to=robert.foss@linaro.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=macromorgan@hotmail.com \
--cc=narmstrong@baylibre.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.