From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] separate i915 changes from existing commits
Date: Mon, 2 Oct 2023 10:34:43 -0400 [thread overview]
Message-ID: <ZRrVA8cjMi4lo6De@intel.com> (raw)
In-Reply-To: <87leclguc9.fsf@intel.com>
On Mon, Oct 02, 2023 at 02:03:02PM +0300, Jani Nikula wrote:
>
> Some commits have slipped through where we modify core xe and i915 in
> the same commits. They'll become a problem when the commit order is
> modified for upstreaming, core first and i915 (display) changes next. To
> that end, I split them out [1]. The commit messages are dumb, but act as
> fixmes.
>
> Rodrigo, can you pick this up and push out? There's no diff to current
> drm-xe-next. If you need modifications, it's not a big deal for me to
> redo this.
Great idea! I just reviewed with git range-diff and force-pushed.
>
>
> BR,
> Jani.
>
>
> [1] https://gitlab.freedesktop.org/jani/xe/-/commits/xe-i915-commit-split-2023-10-02
>
> --
> Jani Nikula, Intel
prev parent reply other threads:[~2023-10-02 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 11:03 [Intel-xe] separate i915 changes from existing commits Jani Nikula
2023-10-02 14:34 ` 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=ZRrVA8cjMi4lo6De@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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.