All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	igt-dev@lists.freedesktop.org,
	Ashutosh Dixit <ashutosh.dixit@intel.com>,
	Matthew Brost <matthew.brost@intel.com>
Subject: Re: [igt-dev] [PATCH v2 i-g-t] drm-uapi/xe_drm: Sync from drm-xe-next
Date: Fri, 23 Jun 2023 11:24:15 -0700	[thread overview]
Message-ID: <87pm5mrq9c.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230623180333.tq5v34uynza46fwu@kamilkon-desk1>

On Fri, 23 Jun 2023 11:03:33 -0700, Kamil Konieczny wrote:
>

Hi Kamil,

> On 2023-06-22 at 20:24:37 -0700, Ashutosh Dixit wrote:
> > Our include/drm-uapi/xe_drm.h is from March. Pull in the latest xe_drm.h
> > from drm-xe-next kernel branch. Generated after 'make headers_install'.
>
> I checked xe_drm.h header and it is a little different. Am I missing
> something ?

What is different? I just posted a v3 with Matt Auld's change to xe_drm.h
from yesterday. Apart from that the file is exactly the same as that in the
kernel, of course we need to do a 'make headers_install' before exposing to
userland.

> There was also patch from Matthew Brost, I will add him to Cc.

Not sure about this one either. Is this something in flight?

> This is still better to have new header, so
>
> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>

Thanks, I'll wait till all these issues are addressed.

Thanks.
--
Ashutosh

      reply	other threads:[~2023-06-23 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  3:24 [igt-dev] [PATCH v2 i-g-t] drm-uapi/xe_drm: Sync from drm-xe-next Ashutosh Dixit
2023-06-23  7:11 ` [igt-dev] ✓ Fi.CI.BAT: success for drm-uapi/xe_drm: Sync from drm-xe-next (rev2) Patchwork
2023-06-23 11:16 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-06-23 18:03 ` [igt-dev] [PATCH v2 i-g-t] drm-uapi/xe_drm: Sync from drm-xe-next Kamil Konieczny
2023-06-23 18:24   ` Dixit, Ashutosh [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=87pm5mrq9c.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=matthew.brost@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 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.