Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Paul <sean@poorly.run>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Sean Paul <seanpaul@chromium.org>
Subject: Re: [PATCH] drm/i915: Kill the undead i915_gem_batch_pool.c
Date: Wed, 9 Oct 2019 15:12:59 -0400	[thread overview]
Message-ID: <20191009191259.GF85762@art_vandelay> (raw)
In-Reply-To: <157064745334.18808.8929010738713347779@skylake-alporthouse-com>

On Wed, Oct 09, 2019 at 07:57:33PM +0100, Chris Wilson wrote:
> Quoting Sean Paul (2019-10-09 19:53:31)
> > On Thu, Aug 22, 2019 at 7:17 AM Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > >
> > > Quoting Joonas Lahtinen (2019-08-22 12:12:03)
> > > > Quoting Chris Wilson (2019-08-22 09:59:17)
> > > > > You have to cut it off at the neck, otherwise it just reappears in the
> > > > > next merge, like commit 3f866026f0ce ("Merge drm/drm-next
> > > > > into drm-intel-next-queued")
> > > > >
> > > > > References: 3f866026f0ce ("Merge drm/drm-next into drm-intel-next-queued")
> > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > >
> > > > Acked-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > >
> > > And once more the nails have been put back in the coffin.
> > 
> > Months later, a hand reaches out from the grave and says:
> > 
> > Error: Cannot open file ../drivers/gpu/drm/i915/i915_gem_batch_pool.c
> > Error: Cannot open file ../drivers/gpu/drm/i915/i915_gem_batch_pool.c
> > Error: Cannot open file ../drivers/gpu/drm/i915/i915_gem_batch_pool.c
> 
> commit b047463c852272ef9956ad3a4c706f78f8b06c17
> Author: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Date:   Fri Aug 30 11:58:48 2019 +0300
> 
>     drm/i915: Remove link to missing "Batchbuffer Pools" documentation
> 

Ah, that's so much less fun :-)

Thanks for the reference, I look forward to getting it in -misc on the next
backmerge.

Sean

> -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-10-09 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22  6:59 [PATCH] drm/i915: Kill the undead i915_gem_batch_pool.c Chris Wilson
2019-08-22  9:06 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-08-22  9:26 ` ✓ Fi.CI.BAT: success " Patchwork
2019-08-22 11:12 ` [PATCH] " Joonas Lahtinen
2019-08-22 11:17   ` Chris Wilson
2019-10-09 18:53     ` Sean Paul
2019-10-09 18:57       ` Chris Wilson
2019-10-09 19:12         ` Sean Paul [this message]
2019-08-23  2:15 ` ✓ Fi.CI.IGT: success for " Patchwork

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=20191009191259.GF85762@art_vandelay \
    --to=sean@poorly.run \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=seanpaul@chromium.org \
    /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