From: Marco Felsch <m.felsch@pengutronix.de>
To: Robert Foss <robert.foss@linaro.org>
Cc: laurent.pinchart@ideasonboard.com, jernej.skrabec@gmail.com,
jonas@kwiboo.se, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, sam@ravnborg.org,
maxime@cerno.tech, devicetree@vger.kernel.org,
kernel@pengutronix.de, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/6] TI SN65DSI83 Features
Date: Wed, 31 Aug 2022 10:13:30 +0200 [thread overview]
Message-ID: <20220831081330.mvy2ziuci3pklr7k@pengutronix.de> (raw)
In-Reply-To: <CAG3jFyt6A2L0Feeibv_76tVhQ_PjRpowQ=CeJ9FaOOshrEWLuQ@mail.gmail.com>
Hi Robert,
On 22-08-29, Robert Foss wrote:
> Hey Marco,
>
> Sorry about the slow reply.
>
> This series no longer applies on drm-misc-next. Can you rebase this
> series and send it out a v2?
I can but I would rather prefer to get some feedback first. Right now I
just got a minor documentation issue feedback from Alexander.
Regards,
Marco
prev parent reply other threads:[~2022-08-31 8:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 15:05 [PATCH 0/6] TI SN65DSI83 Features Marco Felsch
2022-05-30 15:05 ` [PATCH 1/6] drm/bridge: ti-sn65dsi83: make lvds lane register setup more readable Marco Felsch
2022-05-30 15:05 ` [PATCH 2/6] dt-bindings: drm/bridge: ti-sn65dsi83: add documentation for reverse lvds lanes Marco Felsch
2022-06-05 21:09 ` Rob Herring
2022-05-30 15:05 ` [PATCH 3/6] drm/bridge: ti-sn65dsi83: add support to swap the LVDS data lanes Marco Felsch
2022-05-30 15:05 ` [PATCH 4/6] drm/bridge: ti-sn65dsi83: make use of dev_err_probe Marco Felsch
2022-05-30 15:05 ` [PATCH 5/6] dt-bindings: drm/bridge: ti-sn65dsi83: Add reset controller documentation Marco Felsch
2022-05-31 7:33 ` (EXT) " Alexander Stein
2022-05-31 8:29 ` Marco Felsch
2022-05-30 15:05 ` [PATCH 6/6] drm/bridge: ti-sn65dsi83: add support for a external reset controller Marco Felsch
2022-07-26 9:12 ` [PATCH 0/6] TI SN65DSI83 Features Marco Felsch
2022-08-29 15:06 ` Robert Foss
2022-08-31 8:13 ` Marco Felsch [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=20220831081330.mvy2ziuci3pklr7k@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=maxime@cerno.tech \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
/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).