From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, torvalds@linux-foundation.org, tglx@linutronix.de,
hpa@zytor.com
Subject: Re: [Intel-gfx] Updated stolen mem patches
Date: Tue, 27 Aug 2013 11:34:55 +0200 [thread overview]
Message-ID: <20130827093454.GJ26909@phenom.ffwll.local> (raw)
In-Reply-To: <1374870772-4592-1-git-send-email-jbarnes@virtuousgeek.org>
On Fri, Jul 26, 2013 at 01:32:50PM -0700, Jesse Barnes wrote:
> These address the comments I've received so far, but omit the new E820
> type for this mem.
>
> Chris's patches could go on top if desired; they add a new type and
> resource reservation function for looking up regions by name. That
> allows us to remove some duplicate code in the driver for finding stolen
> space.
>
> But I think these two are ready as-is. How should we merge them? Just
> through the i915 tree since the first one touches our headers? that and
> there probably won't be conflicts on the early-quirks file; that's not
> touch too often...
Just noticed that these patches aren't in -next yet - somehow I've thought
they'd go in in through the x86 tree.
Ingo et al: Should I merge these through drm-intel-next or will you pick
them up?
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-08-27 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 20:32 Updated stolen mem patches Jesse Barnes
2013-07-26 20:32 ` [PATCH 1/2] drm/i915: split PCI IDs out into i915_drm.h v4 Jesse Barnes
2013-07-26 20:32 ` [PATCH 2/2] x86: add early quirk for reserving Intel graphics stolen memory v5 Jesse Barnes
2013-08-27 9:34 ` Daniel Vetter [this message]
2013-08-27 18:49 ` [Intel-gfx] Updated stolen mem patches H. Peter Anvin
2013-08-29 22:09 ` 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=20130827093454.GJ26909@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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