Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	intel-xe@lists.freedesktop.org
Cc: dim-tools@lists.freedesktop.org, daniel.vetter@ffwll.ch,
	intel-gfx@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] nightly.conf: Add the xe repo to drm-tip
Date: Fri, 22 Dec 2023 13:29:15 +0100	[thread overview]
Message-ID: <d2cbe861-2969-399f-a9cd-fc79060e7f70@linux.intel.com> (raw)
In-Reply-To: <ec58bfd4-2bd8-6a5b-dd01-74815a058c39@linux.intel.com>


On 12/22/23 13:25, Thomas Hellström wrote:
> Hi,
>
> On 12/22/23 13:01, Jani Nikula wrote:
>> On Fri, 22 Dec 2023, Thomas Hellström 
>> <thomas.hellstrom@linux.intel.com> wrote:
>>> Add the xe repo to drm-tip and the dim tools.
>>> For now use the sha1 of the first drm-xe-next pull request for drm-tip,
>>> since that branch tip is currently adapted for our CI testing.
>> I guess we'll need xe CI to switch to drm-tip based testing, and then
>> force push drm-xe-next to drop that core-for-CI thing. But I think it's
>> fine.
>
> Yes, that's in the plan.
>
>>
>> However, please first push v6.7-rc6 to drm-xe-fixes and current drm-next
>> to drm-xe-next-fixes as a starting point. AFAICT the branches don't
>> exist yet.
>
> Yes, I have that queued-up. Still waiting for the right people to wake 
> up, though, since I'm ATM lacking the right to create those branches 
> in the xe repo. I did a dry-run building drm-tip with these patches
s/patches/branches/ ...
> present in a clone of the xe repo for testing purposes...
>
>>
>> Other than that, LGTM.
>
> Thanks,
>
> Thomas
>
>
>>
>> BR,
>> Jani.
>>
>>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>>> Cc: Oded Gabbay <ogabbay@kernel.org>
>>> Cc: daniel.vetter@ffwll.ch
>>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>>> Cc: dim-tools@lists.freedesktop.org
>>> Cc: dri-devel@lists.freedesktop.org
>>> Cc: intel-gfx@lists.freedesktop.org
>>> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>>> ---
>>>   nightly.conf | 7 +++++++
>>>   1 file changed, 7 insertions(+)
>>>
>>> diff --git a/nightly.conf b/nightly.conf
>>> index 24126b61b797..accd3ff2cc39 100644
>>> --- a/nightly.conf
>>> +++ b/nightly.conf
>>> @@ -24,6 +24,10 @@ git://anongit.freedesktop.org/drm-tip
>>>   https://anongit.freedesktop.org/git/drm/drm-tip
>>>   https://anongit.freedesktop.org/git/drm/drm-tip.git
>>>   "
>>> +drm_tip_repos[drm-xe]="
>>> +ssh://git@gitlab.freedesktop.org/drm/xe/kernel.git
>>> +https://gitlab.freedesktop.org/drm/xe/kernel.git
>>> +"
>>>   drm_tip_repos[drm-intel]="
>>>   ssh://git.freedesktop.org/git/drm/drm-intel
>>>   ssh://git.freedesktop.org/git/drm-intel
>>> @@ -65,14 +69,17 @@ drm_tip_config=(
>>>       "drm            drm-fixes"
>>>       "drm-misc        drm-misc-fixes"
>>>       "drm-intel        drm-intel-fixes"
>>> +    "drm-xe            drm-xe-fixes"
>>>         "drm            drm-next"
>>>       "drm-misc        drm-misc-next-fixes"
>>>       "drm-intel        drm-intel-next-fixes"
>>> +    "drm-xe            drm-xe-next-fixes"
>>>         "drm-misc        drm-misc-next"
>>>       "drm-intel        drm-intel-next"
>>>       "drm-intel        drm-intel-gt-next"
>>> +    "drm-xe            drm-xe-next b6e1b7081768"
>>>         "drm-intel        topic/core-for-CI"
>>>       "drm-misc        topic/i915-ttm"

  reply	other threads:[~2023-12-22 12:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 11:36 [PATCH] nightly.conf: Add the xe repo to drm-tip Thomas Hellström
2023-12-22 12:01 ` Jani Nikula
2023-12-22 12:25   ` Thomas Hellström
2023-12-22 12:29     ` Thomas Hellström [this message]
2023-12-22 16:28 ` Lucas De Marchi
2023-12-26 18:30 ` Rodrigo Vivi
2024-01-03 13:50   ` Thomas Hellström
2024-01-04  5:59     ` Lucas De Marchi
2024-01-08 22:13       ` Rodrigo Vivi
2024-01-08 22:22         ` Lucas De Marchi
2024-01-09 13:46           ` Thomas Hellström
2024-01-08 22:15     ` Rodrigo Vivi

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=d2cbe861-2969-399f-a9cd-fc79060e7f70@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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