From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Vetter <daniel@ffwll.ch>, 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
Subject: Re: [Intel-gfx] Updated stolen mem patches
Date: Tue, 27 Aug 2013 13:49:08 -0500 [thread overview]
Message-ID: <52896c00-6711-4558-9754-e1bba1f81078@email.android.com> (raw)
In-Reply-To: <20130827093454.GJ26909@phenom.ffwll.local>
If noone hers to them first poke me tomorrow. On an aircraft right now.
Daniel Vetter <daniel@ffwll.ch> wrote:
>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
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2013-08-27 18:49 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 ` [Intel-gfx] Updated stolen mem patches Daniel Vetter
2013-08-27 18:49 ` H. Peter Anvin [this message]
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=52896c00-6711-4558-9754-e1bba1f81078@email.android.com \
--to=hpa@zytor.com \
--cc=daniel@ffwll.ch \
--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