From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: <tessolveupstream@gmail.com>, <andrzej.hajda@intel.com>,
<neil.armstrong@linaro.org>, <rfoss@kernel.org>
Cc: <Laurent.pinchart@ideasonboard.com>, <jonas@kwiboo.se>,
<jernej.skrabec@gmail.com>, <maarten.lankhorst@linux.intel.com>,
<mripard@kernel.org>, <tzimmermann@suse.de>, <airlied@gmail.com>,
<simona@ffwll.ch>, <marex@denx.de>, <valentin@compulab.co.il>,
<philippe.schenker@toradex.com>,
<alexander.stein@ew.tq-group.com>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/1] drm: bridge: ti-sn65dsi83: Fix DSI mode flags for stable LVDS output
Date: Wed, 20 May 2026 19:48:31 +0200 [thread overview]
Message-ID: <DINOYRHFLDMD.1TD43L37DHA0T@bootlin.com> (raw)
In-Reply-To: <8a78aab6-918a-4bed-a913-05ecb559da4f@gmail.com>
On Wed May 20, 2026 at 2:29 PM CEST, tessolveupstream wrote:
>>> Additionally, regarding the Tested-by tags you mentioned earlier,
>>> should I carry them forward to both patches, or would you prefer them
>>> only on the applicable patch?
>>
>> I'd say yes. People who sent these tags have tested a patch that is the sum
>> of the two future patches, so I'd say it's OK to keep the R-by on both
>> patches.
>>
>
> Okay, I just wanted to confirm one point — when you mentioned R-by, are you
> referring to the Reviewed-by tag? I wanted to make sure I understood it
> correctly before carrying the tags forward in the next version. 🙂> Thanks for your patience. We'll get to the bottom of this issue! :)
Oops, I wrote R-by but I meant Tested-by.
I don't think you received any other (Acked/Reviewed-by) tags.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-05-20 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 5:38 [PATCH v3 0/1] drm: bridge: ti-sn65dsi83: Fix DSI mode flags for stable LVDS output Sudarshan Shetty
2026-04-12 5:38 ` [PATCH v3 1/1] " Sudarshan Shetty
2026-04-15 7:13 ` Luca Ceresoli
2026-04-15 8:07 ` Luca Ceresoli
2026-04-16 9:10 ` tessolveupstream
2026-04-21 6:01 ` tessolveupstream
2026-04-23 9:16 ` tessolveupstream
2026-04-24 8:25 ` Luca Ceresoli
2026-05-19 8:48 ` tessolveupstream
2026-05-19 11:43 ` Luca Ceresoli
2026-05-20 9:04 ` tessolveupstream
2026-05-20 11:38 ` Luca Ceresoli
2026-05-20 12:29 ` tessolveupstream
2026-05-20 17:48 ` Luca Ceresoli [this message]
2026-05-21 6:30 ` tessolveupstream
2026-04-15 13:51 ` Alexander Stein
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=DINOYRHFLDMD.1TD43L37DHA0T@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=philippe.schenker@toradex.com \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tessolveupstream@gmail.com \
--cc=tzimmermann@suse.de \
--cc=valentin@compulab.co.il \
/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.