From: Jani Nikula <jani.nikula@intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/connector: document enum drm_connector_tv_mode DRM_MODE_TV_MODE_MAX
Date: Tue, 09 May 2023 12:35:40 +0300 [thread overview]
Message-ID: <875y91onir.fsf@intel.com> (raw)
In-Reply-To: <xAFAkPUUOOBaOeo-gUC5Cie_-c8lebcFKZD7CYPMIJP_6fy8dla0m68EYtWtQAAayuNIftrpBJkHFEHJaUrV-MyO_xJvWiErwJ2NAkQuLMA=@emersion.fr>
On Thu, 04 May 2023, Simon Ser <contact@emersion.fr> wrote:
> Reviewed-by: Simon Ser <contact@emersion.fr>
Thanks, pushed to drm-misc-next.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/connector: document enum drm_connector_tv_mode DRM_MODE_TV_MODE_MAX
Date: Tue, 09 May 2023 12:35:40 +0300 [thread overview]
Message-ID: <875y91onir.fsf@intel.com> (raw)
In-Reply-To: <xAFAkPUUOOBaOeo-gUC5Cie_-c8lebcFKZD7CYPMIJP_6fy8dla0m68EYtWtQAAayuNIftrpBJkHFEHJaUrV-MyO_xJvWiErwJ2NAkQuLMA=@emersion.fr>
On Thu, 04 May 2023, Simon Ser <contact@emersion.fr> wrote:
> Reviewed-by: Simon Ser <contact@emersion.fr>
Thanks, pushed to drm-misc-next.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-05-09 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 12:34 [Intel-gfx] [PATCH] drm/connector: document enum drm_connector_tv_mode DRM_MODE_TV_MODE_MAX Jani Nikula
2023-05-04 12:34 ` Jani Nikula
2023-05-04 13:02 ` [Intel-gfx] " Simon Ser
2023-05-04 13:02 ` Simon Ser
2023-05-09 9:35 ` Jani Nikula [this message]
2023-05-09 9:35 ` Jani Nikula
2023-05-04 20:23 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-05-04 20:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-05 6:49 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=875y91onir.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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.