From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>,
Matthew Auld <matthew.auld@intel.com>,
Dave Airlie <airlied@gmail.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
intel-gfx@lists.freedesktop.org, x86@kernel.org,
dri-devel@lists.freedesktop.org,
"H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/6] drm/i915: export the stolen region as a resource
Date: Thu, 23 Nov 2017 09:48:04 +0200 [thread overview]
Message-ID: <1511423284.4641.9.camel@linux.intel.com> (raw)
In-Reply-To: <20171123061746.fubq4baj46qacamr@gmail.com>
+ Dave as a heads-up
On Thu, 2017-11-23 at 07:17 +0100, Ingo Molnar wrote:
> * Matthew Auld <matthew.auld@intel.com> wrote:
>
> > We duplicate the stolen discovery code in early-quirks and in i915,
> > however if we just export the region as a resource from early-quirks we
> > can nuke the duplication.
> >
> > Suggested-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > Cc: Ingo Molnar <mingo@kernel.org>
> > Cc: H. Peter Anvin <hpa@zytor.com>
> > Cc: dri-devel@lists.freedesktop.org
> > Cc: x86@kernel.org
> > ---
> > arch/x86/kernel/early-quirks.c | 6 ++
> > drivers/gpu/drm/i915/i915_gem_gtt.c | 51 +--------------
> > drivers/gpu/drm/i915/i915_gem_stolen.c | 109 +--------------------------------
> > include/drm/i915_drm.h | 3 +
> > 4 files changed, 13 insertions(+), 156 deletions(-)
>
> If it's truly identical:
>
> Acked-by: Ingo Molnar <mingo@kernel.org>
Are you fine with us merging this together with the rest of the series
through the DRM tree once it's all reviewed?
That'd help not requiring so many backmerges.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-23 7:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 21:19 [PATCH 0/6] make stolen resource centric Matthew Auld
2017-11-22 21:19 ` [PATCH 1/6] drm/i915: export the stolen region as a resource Matthew Auld
2017-11-23 6:17 ` Ingo Molnar
2017-11-23 7:48 ` Joonas Lahtinen [this message]
2017-11-23 7:59 ` Ingo Molnar
2017-11-24 7:52 ` Joonas Lahtinen
2017-11-22 21:19 ` [PATCH 2/6] drm/i915: s/mappable_end/mappable_size/ Matthew Auld
2017-11-22 21:43 ` Chris Wilson
2017-11-23 10:23 ` Matthew Auld
2017-11-22 21:19 ` [PATCH 3/6] drm/i915: make dsm struct resource centric Matthew Auld
2017-11-23 13:03 ` Chris Wilson
2017-11-22 21:19 ` [PATCH 4/6] drm/i915: make reserved " Matthew Auld
2017-11-23 13:05 ` Chris Wilson
2017-11-22 21:19 ` [PATCH 5/6] drm/i915: make mappable " Matthew Auld
2017-11-23 13:06 ` Chris Wilson
2017-11-22 21:19 ` [PATCH 6/6] drm/i915: prefer resource_size_t for stolen sizes Matthew Auld
2017-11-23 13:07 ` Chris Wilson
2017-11-22 21:48 ` ✓ Fi.CI.BAT: success for make stolen resource centric Patchwork
2017-11-22 22:26 ` ✗ Fi.CI.IGT: warning " 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=1511423284.4641.9.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=mingo@kernel.org \
--cc=paulo.r.zanoni@intel.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).