dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/edid & drm/display header spring cleaning
Date: Mon, 08 Apr 2024 11:59:36 +0300	[thread overview]
Message-ID: <87cyr0b56v.fsf@intel.com> (raw)
In-Reply-To: <cover.1711014272.git.jani.nikula@intel.com>

On Thu, 21 Mar 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> Jani Nikula (3):
>   drm/displayid: move drm_displayid.h to drm_displayd_internal.h
>   drm/edid: move all internal declarations to drm_crtc_internal.h
>   drm/edid: group struct drm_edid based declarations together

Resent as part of https://patchwork.freedesktop.org/series/132142/

>
>  drivers/gpu/drm/drm_crtc_internal.h                   |  6 ++++++
>  drivers/gpu/drm/drm_displayid.c                       |  4 +++-
>  .../gpu/drm/drm_displayid_internal.h                  |  5 +++--
>  drivers/gpu/drm/drm_edid.c                            |  2 +-
>  drivers/gpu/drm/drm_eld.c                             |  4 +++-
>  drivers/gpu/drm/drm_internal.h                        |  5 -----
>  include/drm/drm_edid.h                                | 11 ++++-------
>  7 files changed, 20 insertions(+), 17 deletions(-)
>  rename include/drm/drm_displayid.h => drivers/gpu/drm/drm_displayid_internal.h (98%)

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2024-04-08  8:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21  9:45 [PATCH 0/3] drm/edid & drm/display header spring cleaning Jani Nikula
2024-03-21  9:45 ` [PATCH 1/3] drm/displayid: move drm_displayid.h to drm_displayd_internal.h Jani Nikula
2024-03-21  9:45 ` [PATCH 2/3] drm/edid: move all internal declarations to drm_crtc_internal.h Jani Nikula
2024-03-21  9:45 ` [PATCH 3/3] drm/edid: group struct drm_edid based declarations together Jani Nikula
2024-04-08  8:59 ` 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=87cyr0b56v.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --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 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).