All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Matthew Auld <matthew.auld@intel.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Kill the fake lmem support
Date: Fri, 18 Feb 2022 22:34:30 -0800	[thread overview]
Message-ID: <20220219063430.me564f4lu4ufpb6g@ldmartin-desk2> (raw)
In-Reply-To: <CAM0jSHM3cf36p_+V3Nx-6mKzARkfPjcPVKnxmx49wUcRKo5bbQ@mail.gmail.com>

On Thu, Feb 17, 2022 at 06:09:53PM +0000, Matthew Auld wrote:
>On Thu, 17 Feb 2022 at 17:55, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
>>
>> This was useful for early development of lmem, but it's not used
>> anymore, so remove it.
>>
>> v2: Remove unneeded fields from struct intel_memory_region
>>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Matthew Auld <matthew.auld@intel.com>
>> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
>Reviewed-by: Matthew Auld <matthew.auld@intel.com>

Thanks, applied.

Lucas De Marchi

  reply	other threads:[~2022-02-19  6:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 17:56 [PATCH v2] drm/i915: Kill the fake lmem support Lucas De Marchi
2022-02-17 17:56 ` [Intel-gfx] " Lucas De Marchi
2022-02-17 18:09 ` Matthew Auld
2022-02-17 18:09   ` [Intel-gfx] " Matthew Auld
2022-02-19  6:34   ` Lucas De Marchi [this message]
2022-02-18  2:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Kill the fake lmem support (rev2) Patchwork
2022-02-18  2:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-18 13:08 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-19  6:29   ` Lucas De Marchi

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=20220219063430.me564f4lu4ufpb6g@ldmartin-desk2 \
    --to=lucas.demarchi@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.william.auld@gmail.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.