From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
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, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] nightly.conf: Add the xe repo to drm-tip
Date: Mon, 8 Jan 2024 17:15:51 -0500 [thread overview]
Message-ID: <ZZx0F5w6COxVcBVz@intel.com> (raw)
In-Reply-To: <9541c844440e8b0fc5686e19850a04c7a55745ba.camel@linux.intel.com>
On Wed, Jan 03, 2024 at 02:50:57PM +0100, Thomas Hellström wrote:
> On Tue, 2023-12-26 at 13:30 -0500, Rodrigo Vivi wrote:
> > On Fri, Dec 22, 2023 at 12:36:39PM +0100, Thomas Hellström 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.
> > >
> > > 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"
> >
> > yeap, up to this commit nothing else should change, but
> > then we will need an extra rebase of the rest on top of drm/drm-next.
> >
> > But then we need to decide where these following patches will live:
> > 880277f31cc69 drm/xe/guc: define LNL FW
> > 2cfc5ae1b8267 drm/xe/guc: define PVC FW
> > 52383b58eb8cf mei/hdcp: Also enable for XE
> > bea27d7369855 mei: gsc: add support for auxiliary device created by
> > Xe driver
> > fcb3410197f05 fault-inject: Include linux/types.h by default.
> > 8ebd9cd71f8ac drm/xe: Add PVC's PCI device IDs
> >
> >
> > Will it be the topic/core-for-CI?
> > or topic/xe-extras?
> > or what?
>
> This sounds to me like topic/core-for-CI? Or is there any drawback with
> that?
>
> >
> > Anyway, for the inclusion like this, after our CI is ready:
>
> Could we merge this patch already at this point, considering it will,
> at least for now, only update drm-tip with our fixes?
yeap, likely a good idea.
Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
But we just move the final drm-xe-next after figuring out the topic
branches and the final rebases fixing the tags and the commiter's s-o-b
and the fixes tags.
>
> Thanks,
>
> /Thomas
>
>
> >
> > Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >
> > >
> > > "drm-intel topic/core-for-CI"
> > > "drm-misc topic/i915-ttm"
> > > --
> > > 2.42.0
> > >
>
prev parent reply other threads:[~2024-01-08 22:16 UTC|newest]
Thread overview: 16+ 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 11:36 ` Thomas Hellström
2023-12-22 12:01 ` Jani Nikula
2023-12-22 12:01 ` Jani Nikula
2023-12-22 12:25 ` Thomas Hellström
2023-12-22 12:25 ` Thomas Hellström
2023-12-22 12:29 ` Thomas Hellström
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: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 [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=ZZx0F5w6COxVcBVz@intel.com \
--to=rodrigo.vivi@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=lucas.demarchi@intel.com \
--cc=thomas.hellstrom@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 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.