From: Daniel Vetter <daniel@ffwll.ch>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/3] Clean a few backend interfaces in the i915
Date: Wed, 26 May 2021 19:11:01 +0200 [thread overview]
Message-ID: <YK6BJbKteLFGg92r@phenom.ffwll.local> (raw)
In-Reply-To: <20210525155438.GB6585@sdutt-i7>
On Tue, May 25, 2021 at 08:54:38AM -0700, Matthew Brost wrote:
> On Tue, May 25, 2021 at 04:27:49PM +0100, Tvrtko Ursulin wrote:
> >
> > On 25/05/2021 14:56, Daniel Vetter wrote:
> > > On Fri, May 21, 2021 at 11:32:12AM -0700, Matthew Brost wrote:
> > > > As discussed in [1] start merging some support patches as a precursor to
> > > > GuC submission the i915. This is step #1 mentioned in [1].
> > > >
> > > > [1] https://patchwork.freedesktop.org/series/89844/
> > > >
> > > > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > >
> > > Pushed to drm-intel-gt-next, thanks for patches&reviews. Btw you can also
> > > ping John H or Daniele for pushing stuff for you, should be quicker than
> > > waiting for me to return from a lon w/e :-)
> > >
> > > Plus I _really_ don't want to get back into the business of pushing other
> > > people's work ...
> >
> > To Matt - Also please take care to preserve r-b's when resurrecting patches
> > because all of these three had mine from before which is now lost in git
> > history.
> >
>
> Will do. Still getting used to the upstream rules and wasn't sure if
> should have included your old R-Bs.
If you have an r-b but for an old version with some significant changes
compared to the current one add a (v1) or similar tag at the end of that
r-b. That way it's not lost, but also not misattributed to a newer and
potentially buggy version of the patch.
-Daniel
>
> Matt
>
> > Regards,
> >
> > Tvrtko
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-26 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 18:32 [Intel-gfx] [PATCH 0/3] Clean a few backend interfaces in the i915 Matthew Brost
2021-05-21 18:32 ` [Intel-gfx] [PATCH 1/3] drm/i915/gt: Move engine setup out of set_default_submission Matthew Brost
2021-05-21 18:32 ` [Intel-gfx] [PATCH 2/3] drm/i915/gt: Move submission_method into intel_gt Matthew Brost
2021-05-21 18:32 ` [Intel-gfx] [PATCH 3/3] drm/i915/gt: Move CS interrupt handler to the backend Matthew Brost
2021-05-21 19:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Clean a few backend interfaces in the i915 Patchwork
2021-05-24 3:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-05-25 13:56 ` [Intel-gfx] [PATCH 0/3] " Daniel Vetter
2021-05-25 15:27 ` Tvrtko Ursulin
2021-05-25 15:54 ` Matthew Brost
2021-05-26 17:11 ` Daniel Vetter [this message]
2021-05-25 15:53 ` Matthew Brost
2021-05-26 17:15 ` Daniel Vetter
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=YK6BJbKteLFGg92r@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox