From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] include/drm-uapi: Update uapi headers
Date: Wed, 2 Oct 2024 13:03:03 +0300 [thread overview]
Message-ID: <Zv0aV6gKOmrJFaRj@intel.com> (raw)
In-Reply-To: <20240925192354.22814-1-ville.syrjala@linux.intel.com>
On Wed, Sep 25, 2024 at 10:23:54PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Sync uapi headers with drm-next commit d7126c0cfc13
> ("Merge tag 'drm-xe-next-fixes-2024-09-19' of
> https://gitlab.freedesktop.org/drm/xe/kernel into drm-next")
>
> Note that headers for old dri1 drivers are now gone,
> and we gain a bunch of new headers for various
> new drivers (gpu and accel).
>
> I manually intervened on the deletion of
> include/drm-uapi/xe_drm_eudebug.h because it's some
> non-upstream thing. IMO that sort of stuff really
> should live in a completely different place...
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Ping. Can someone toss me an ack/rb?
I'd like to finally merge the plane SIZE_HINT uapi tests but
I need the new headers for that...
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-10-02 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 19:23 [PATCH i-g-t] include/drm-uapi: Update uapi headers Ville Syrjala
2024-09-26 8:52 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-09-26 9:15 ` ✗ CI.xeBAT: " Patchwork
2024-09-27 0:06 ` ✗ CI.xeFULL: " Patchwork
2024-09-30 18:48 ` ✓ Fi.CI.BAT: success for include/drm-uapi: Update uapi headers (rev2) Patchwork
2024-09-30 19:16 ` ✗ CI.xeBAT: failure " Patchwork
2024-10-01 1:15 ` ✗ CI.xeFULL: " Patchwork
2024-10-01 4:35 ` ✗ Fi.CI.IGT: " Patchwork
2024-10-02 10:03 ` Ville Syrjälä [this message]
2024-10-02 10:15 ` [PATCH i-g-t] include/drm-uapi: Update uapi headers Kamil Konieczny
2024-10-02 10:20 ` Ville Syrjälä
2024-10-02 14:14 ` Kamil Konieczny
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=Zv0aV6gKOmrJFaRj@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@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