From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/8] drm: Clean up drm_crtc.h
Date: Tue, 14 Jun 2022 11:04:03 +0300 [thread overview]
Message-ID: <877d5jzn64.fsf@intel.com> (raw)
In-Reply-To: <20220613200317.11305-1-ville.syrjala@linux.intel.com>
On Mon, 13 Jun 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Eliminate unnecessary includes from drm_crtc.h to avoid
> pointless rebuilds of the entire universe when touching
> some random header.
>
> I didn't really feel like splitting this up per-driver since
> that would have ended up being metric ton of one liners.
> I'm thinking the conflicts (if any) should be trivial enough
> to deal with even with bigger patches.
>
> Also the cc list would have been massive so didn't do it.
> Hopefully enough people actually read dri-devel...
Seems like a good idea to me. FWIW,
Acked-by: Jani Nikula <jani.nikula@intel.com>
Both the CI and the kernel bot found some issues, obviously those need
to be addressed, but otherwise I'd just rely on build results for
merging.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-06-14 8:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 20:03 [Intel-gfx] [PATCH 0/8] drm: Clean up drm_crtc.h Ville Syrjala
2022-06-13 20:03 ` [Intel-gfx] [PATCH 1/8] drm: Drop drm_edid.h from drm_crtc.h Ville Syrjala
2022-06-14 9:02 ` [Intel-gfx] [PATCH v2 " Ville Syrjala
2022-06-15 19:38 ` [Intel-gfx] [PATCH " Sam Ravnborg
2022-06-13 20:03 ` [Intel-gfx] [PATCH 2/8] drm: Drop drm_framebuffer.h " Ville Syrjala
2022-06-13 23:24 ` kernel test robot
2022-06-14 0:05 ` kernel test robot
2022-06-14 9:03 ` [Intel-gfx] [PATCH v2 " Ville Syrjala
2022-06-14 9:54 ` [Intel-gfx] [PATCH v3 " Ville Syrjala
2022-06-15 19:41 ` Sam Ravnborg
2022-06-13 20:03 ` [Intel-gfx] [PATCH 3/8] drm: Drop drm_blend.h " Ville Syrjala
2022-06-15 19:45 ` Sam Ravnborg
2022-06-13 20:03 ` [Intel-gfx] [PATCH 4/8] drm: Drop drm_connector.h " Ville Syrjala
2022-06-13 20:03 ` [Intel-gfx] [PATCH 5/8] drm: Remove unnecessary junk " Ville Syrjala
2022-06-13 20:03 ` [Intel-gfx] [PATCH 6/8] drm: Remove linux/fb.h " Ville Syrjala
2022-06-13 20:03 ` [Intel-gfx] [PATCH 7/8] drm: Remove linux/media-bus-format.h " Ville Syrjala
2022-06-14 0:05 ` kernel test robot
2022-06-14 0:56 ` kernel test robot
2022-06-14 9:56 ` [Intel-gfx] [PATCH v3 " Ville Syrjala
2022-06-13 20:03 ` [Intel-gfx] [PATCH 8/8] drm: Remove linux/i2c.h " Ville Syrjala
2022-06-14 1:38 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: Clean up drm_crtc.h Patchwork
2022-06-14 8:04 ` Jani Nikula [this message]
2022-06-14 15:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm: Clean up drm_crtc.h (rev5) Patchwork
2022-06-15 5:17 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-06-15 19:48 ` [Intel-gfx] [PATCH 0/8] drm: Clean up drm_crtc.h Sam Ravnborg
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=877d5jzn64.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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