From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe@lists.freedesktop.org
Cc: karol.krol@intel.com, maciej.ramotowski@intel.com,
michal.czaplinski@intel.com, ryszard.knop@intel.com
Subject: Re: [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/8] drm/i915/display: don't use relative ../i915 includes
Date: Fri, 03 Mar 2023 11:27:46 +0200 [thread overview]
Message-ID: <877cvyuqul.fsf@intel.com> (raw)
In-Reply-To: <20230302174735.nstcblrzbhuwbhox@ldmartin-desk2.lan>
On Thu, 02 Mar 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Thu, Mar 02, 2023 at 02:26:46PM -0000, Patchwork wrote:
>>== Series Details ==
>>
>>Series: series starting with [1/8] drm/i915/display: don't use relative ../i915 includes
>>URL : https://patchwork.freedesktop.org/series/114573/
>>State : success
>
> Cc'ing some more people. Some nice additions here:
>
> 1) The base commit used for applying the patch.
> 2) Maybe push to a repo as refs/heads/<sanitized-msg-id> and add the
> link to it here, so if the developer wants to check what exactly CI was
> using in the build it's just one command away? Those refs could be
> cleaned up every few months so the repo doesn't grow indefinitely
Somewhat related, I think CONFIG_DRM_XE_DISPLAY is currently brittle
enough that we need to build both =y and =n to keep this working.
I'm doing this locally for my stuff, but I don't expect everyone will.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-03 9:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 14:12 [Intel-xe] [PATCH 0/8] drm/xe: clean up i915 includes both sides Jani Nikula
2023-03-02 14:12 ` [Intel-xe] [PATCH 1/8] drm/i915/display: don't use relative ../i915 includes Jani Nikula
2023-03-02 15:28 ` Lucas De Marchi
2023-03-02 15:45 ` Jani Nikula
2023-03-02 18:00 ` Lucas De Marchi
2023-03-02 14:12 ` [Intel-xe] [PATCH 2/8] drm/i915/display: drop redundant display/ from includes Jani Nikula
2023-03-02 14:12 ` [Intel-xe] [PATCH 3/8] drm/xe: drop unnecessary include Jani Nikula
2023-03-03 6:07 ` Lucas De Marchi
2023-03-02 14:12 ` [Intel-xe] [PATCH 4/8] drm/xe: drop redundant display/ from includes Jani Nikula
2023-03-02 14:12 ` [Intel-xe] [PATCH 5/8] drm/xe: drop redundant ../ " Jani Nikula
2023-03-02 14:12 ` [Intel-xe] [PATCH 6/8] drm/xe: move all top level i915 compat headers to a separate subdirectory Jani Nikula
2023-03-03 6:10 ` Lucas De Marchi
2023-03-02 14:12 ` [Intel-xe] [PATCH 7/8] drm/xe: remove unnecessary include Jani Nikula
2023-03-02 14:12 ` [Intel-xe] [PATCH 8/8] drm/xe: drop top level i915 from include path Jani Nikula
2023-03-03 6:21 ` Lucas De Marchi
2023-03-03 6:30 ` Lucas De Marchi
2023-03-02 14:26 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/8] drm/i915/display: don't use relative ../i915 includes Patchwork
2023-03-02 17:47 ` Lucas De Marchi
2023-03-03 9:27 ` Jani Nikula [this message]
2023-03-02 14:27 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-02 14:30 ` [Intel-xe] ✗ CI.Build: failure " Patchwork
2023-03-02 14:57 ` Jani Nikula
2023-03-02 15:07 ` Jani Nikula
2023-03-03 6:28 ` [Intel-xe] [PATCH 0/8] drm/xe: clean up i915 includes both sides Lucas De Marchi
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=877cvyuqul.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karol.krol@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maciej.ramotowski@intel.com \
--cc=michal.czaplinski@intel.com \
--cc=ryszard.knop@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