All of lore.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben@geanix.com>
To: "Markus Elfring" <Markus.Elfring@web.de>
Cc: <dri-devel@lists.freedesktop.org>,  <stable@vger.kernel.org>,
	 "LKML" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/3] drm/bridge: ti-sn65dsi83: Propagate error in sn65dsi83_reset_pipe()
Date: Tue, 25 Aug 2026 10:47:12 +0200	[thread overview]
Message-ID: <87se42oacv.fsf@geanix.com> (raw)
In-Reply-To: <2f0fef87-4377-4a01-a210-8d55a0b67a9e@web.de> (Markus Elfring's message of "Wed, 19 Aug 2026 13:51:13 +0200")

"Markus Elfring" <Markus.Elfring@web.de> writes:

>> Propagate the error code from drm_bridge_helper_reset_crtc(), so that
>> callers has a chance to handle the failure.
>
>           have got?

I will change to "so that callers have a chance ...", for proper
plural form. Thanks.

/Esben

  reply	other threads:[~2026-08-25  8:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10  7:19 [PATCH v4 0/3] drm/bridge: ti-sn65dsi83: Various fixes Esben Haabendal
2026-08-10  7:19 ` [PATCH v4 1/3] drm/bridge: ti-sn65dsi83: Fix error handling in sn65dsi83_reset_work() Esben Haabendal
2026-08-10  7:29   ` sashiko-bot
2026-08-19  9:32   ` Herve Codina
2026-08-25  9:01     ` Esben Haabendal
2026-08-28 12:15     ` Esben Haabendal
2026-08-28 14:55       ` Esben Haabendal
2026-08-10  7:19 ` [PATCH v4 2/3] drm/bridge: ti-sn65dsi83: Propagate error in sn65dsi83_reset_pipe() Esben Haabendal
2026-08-10  7:36   ` sashiko-bot
2026-08-19  9:36   ` Herve Codina
2026-08-19 11:51   ` Markus Elfring
2026-08-25  8:47     ` Esben Haabendal [this message]
2026-08-10  7:19 ` [PATCH v4 3/3] drm/bridge: ti-sn65dsi83: Support LVDS Channel B on SN65DSI84 Esben Haabendal
2026-08-19 11:57   ` Markus Elfring
2026-08-25  8:43     ` Esben Haabendal

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=87se42oacv.fsf@geanix.com \
    --to=esben@geanix.com \
    --cc=Markus.Elfring@web.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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 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.