From: Frank Oltmanns <frank@oltmanns.dev>
To: "Ondřej Jirman" <megi@xff.cz>
Cc: "Purism Kernel Team" <kernel@puri.sm>,
"Samuel Holland" <samuel@sholland.org>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Guido Günther" <agx@sigxcpu.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
"Thierry Reding" <thierry.reding@gmail.com>
Subject: Re: [PATCH 1/1] drm/panel: st7703: Fix resume of XBD599 panel
Date: Sun, 12 Feb 2023 14:15:43 +0100 [thread overview]
Message-ID: <875yc70yxy.fsf@oltmanns.dev> (raw)
In-Reply-To: <20230212123621.jo56yqlburd6g6ir@core>
WARNING: multiple messages have this Message-ID (diff)
From: Frank Oltmanns <frank@oltmanns.dev>
To: "Ondřej Jirman" <megi@xff.cz>
Cc: "Guido Günther" <agx@sigxcpu.org>,
"Purism Kernel Team" <kernel@puri.sm>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Samuel Holland" <samuel@sholland.org>
Subject: Re: [PATCH 1/1] drm/panel: st7703: Fix resume of XBD599 panel
Date: Sun, 12 Feb 2023 14:15:43 +0100 [thread overview]
Message-ID: <875yc70yxy.fsf@oltmanns.dev> (raw)
In-Reply-To: <20230212123621.jo56yqlburd6g6ir@core>
next prev parent reply other threads:[~2023-02-12 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 12:08 [PATCH 0/1] drm/panel: st7703: Fix resume of XBD599 panel Frank Oltmanns
2023-02-12 12:08 ` [PATCH 1/1] " Frank Oltmanns
2023-02-12 12:08 ` Frank Oltmanns
2023-02-12 12:36 ` Ondřej Jirman
2023-02-12 12:36 ` Ondřej Jirman
2023-02-12 13:15 ` Frank Oltmanns [this message]
2023-02-12 13:15 ` Frank Oltmanns
2023-02-12 17:52 ` Frank Oltmanns
2023-02-12 17:52 ` Frank Oltmanns
2023-02-12 19:35 ` Ondřej Jirman
2023-02-12 19:35 ` Ondřej Jirman
2023-02-13 7:47 ` Frank Oltmanns
2023-02-13 7:47 ` Frank Oltmanns
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=875yc70yxy.fsf@oltmanns.dev \
--to=frank@oltmanns.dev \
--cc=agx@sigxcpu.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@puri.sm \
--cc=linux-kernel@vger.kernel.org \
--cc=megi@xff.cz \
--cc=sam@ravnborg.org \
--cc=samuel@sholland.org \
--cc=thierry.reding@gmail.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.