From: Jani Nikula <jani.nikula@intel.com>
To: "대인기/Tizen Platform Lab(SR)/삼성전자" <inki.dae@samsung.com>,
dri-devel@lists.freedesktop.org
Cc: 'Daniel Vetter' <daniel.vetter@intel.com>
Subject: RE: [PATCH 0/6] drm: conversions to struct drm_edid
Date: Wed, 04 Sep 2024 11:32:41 +0300 [thread overview]
Message-ID: <8734mfu8d2.fsf@intel.com> (raw)
In-Reply-To: <0f9201dafe71$26575c70$73061550$@samsung.com>
On Wed, 04 Sep 2024, 대인기/Tizen Platform Lab(SR)/삼성전자 <inki.dae@samsung.com> wrote:
>> > drm/exynos: hdmi: use display_info for printing display dimensions
>> > drm/exynos: hdmi: convert to struct drm_edid
>>
>> I'll wait for Inki to check these.
>
> You could push them to drm-misc-next.
>
> Acked-by : Inki Dae <inki.dae@samsung.com>
Thanks, pushed.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-09-04 8:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 17:42 [PATCH 0/6] drm: conversions to struct drm_edid Jani Nikula
2024-08-22 17:42 ` [PATCH 1/6] drm/sti/sti_hdmi: convert " Jani Nikula
2024-08-22 17:42 ` [PATCH 2/6] drm/exynos: hdmi: use display_info for printing display dimensions Jani Nikula
2024-08-28 12:44 ` Daniel Vetter
2024-08-22 17:42 ` [PATCH 3/6] drm/exynos: hdmi: convert to struct drm_edid Jani Nikula
2024-08-28 12:45 ` Daniel Vetter
2024-08-22 17:42 ` [PATCH 4/6] drm/tegra: " Jani Nikula
2024-08-28 12:46 ` Daniel Vetter
2024-08-29 8:55 ` Thierry Reding
2024-08-29 11:43 ` Jani Nikula
2024-08-22 17:42 ` [PATCH 5/6] drm/ipuv3/parallel: " Jani Nikula
2024-08-28 12:48 ` Daniel Vetter
2024-08-22 17:42 ` [PATCH 6/6] drm/tiny/gm12u320: " Jani Nikula
2024-08-28 12:49 ` Daniel Vetter
2024-08-28 12:52 ` Thomas Zimmermann
2024-08-28 13:35 ` Jani Nikula
2024-08-29 11:44 ` [PATCH 0/6] drm: conversions " Jani Nikula
2024-09-04 2:21 ` 대인기/Tizen Platform Lab(SR)/삼성전자
2024-09-04 8:32 ` Jani Nikula [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=8734mfu8d2.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.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 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).