From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe: Update to upstream DRM scheduler code
Date: Wed, 25 Oct 2023 17:45:24 -0400 [thread overview]
Message-ID: <ZTmMdCIjRHP0K/SE@intel.com> (raw)
In-Reply-To: <eztcofcj4qwbokg6n2ua4t5okg6f24mksxgkgsewozvdbufe22@bt7pyoxs3s5r>
> > This is based on the upstream series [1] that hopefully gets merged
> > soon. To create this patch I just dropped in the new drm-scheduler code
> > (copied drivers/gpu/drm/scheduler/*.c / *.h into this repo) and updated
> > the Xe code as required. The DRM scheduler coded so much in the baseline
> > I'm not sure if it worth trying to do fixup patches, rather we just
> > merge it on tip and find a proper place these changes during the next
> > rebase. Open to other ideas too.
>
> I don't think we should do fixup patches neither, but it's important to
> keep documented in the commit message how and what was changed. Like you
> did now.
>
> However I think it will be quite troublesome to rebase the branch in
> future since you are also changing other parts of the code. So it's not
> a matter of just dropping this one patch when we rebase. Lately it's
> usually Rodrigo who is rebasing drm-xe-next, so +Rodrigo.
the rebase won't be easy indeed.
Another aspect is that we will likely need to wait that to propagate
from drm-misc-next to drm-next before we can rebase on drm-next and do
the first pull-request.
>
> One alternative that comes to mind is: can you do the rebase and post
> the result to a remote branch? Assuming your remote is called xe:
>
> git fetch xe
> git reset --hard xe/drm-xe-next
> git rebase -i bb46e837b7e59c22a567ae6913ff4d6bf0e9211a
Yes, please! We had a similar situation with the display case and this
is what I asked Jouni to do. Having the reference branch when rebasing
was super helpful.
Besides the reference branch, we need a top commit on drm-xe-next.
(Maybe this commit here?, maybe something more)
But in a way that the
$ git diff drm-xe-next..reference-branch
should be empty
Then we force-push origin/drm-xe-next
and when the rebase on drm-next comes, the drm-sched base patches
will disappear and we won't have any conflict.
>
> Then drop the patches as you see fit and add the ones from this series.
>
> Lucas De Marchi
next prev parent reply other threads:[~2023-10-25 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 4:05 [Intel-xe] [PATCH] drm/xe: Update to upstream DRM scheduler code Matthew Brost
2023-10-25 4:11 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-10-25 4:11 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-25 4:13 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-25 4:20 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-25 4:20 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-25 4:21 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-10-25 4:47 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-10-25 13:56 ` [Intel-xe] [PATCH] " Lucas De Marchi
2023-10-25 17:07 ` Matthew Brost
2023-10-25 17:49 ` Lucas De Marchi
2023-10-25 21:45 ` Rodrigo Vivi [this message]
2023-11-03 3:35 ` 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=ZTmMdCIjRHP0K/SE@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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