From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Matthew Auld <matthew.auld@intel.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
intel-gfx@lists.freedesktop.org, x86@kernel.org,
"H . Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 1/9] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit
Date: Mon, 27 Nov 2017 10:11:33 +0200 [thread overview]
Message-ID: <1511770293.4627.9.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1711250041580.2316@nanos>
On Sat, 2017-11-25 at 00:48 +0100, Thomas Gleixner wrote:
> On Fri, 24 Nov 2017, Matthew Auld wrote:
>
> > From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>
> Please CC the linux kernel mailinglist on patches related to x86. The
> MAINTAINERS file says:
>
> X86 ARCHITECTURE (32-BIT AND 64-BIT)
> M: Thomas Gleixner <tglx@linutronix.de>
> M: Ingo Molnar <mingo@redhat.com>
> M: "H. Peter Anvin" <hpa@zytor.com>
> M: x86@kernel.org
> L: linux-kernel@vger.kernel.org <===========
>
> See also Documentation/process/submitting-patches.rst, chapter:
>
> 5) Select the recipients for your patch
My bad. I lazily copied over the Cc: list from the patch that was meant
to squashed into this patch.
> > In preparation for upcoming SKUs, allow more freedom in placement
> > of the Intel graphics stolen memory by BIOS to full 64bit range.
>
> This is not really informative for people not familiar with the issue you
> want to solve.
"To give upcoming SKU BIOSes more flexibility in placing the Intel
graphics stolen memory, make all variables storing the placement or
size compatible with full 64 bit range."
Does that sound better to you?
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-27 8:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 21:29 [PATCH 0/9] make stolen resource centric Matthew Auld
2017-11-24 21:29 ` [PATCH 1/9] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Matthew Auld
2017-11-24 22:05 ` Chris Wilson
2017-11-27 9:43 ` Joonas Lahtinen
2017-11-24 23:48 ` Thomas Gleixner
2017-11-27 8:11 ` Joonas Lahtinen [this message]
2017-11-24 21:29 ` [PATCH 2/9] x86/early-quirks: replace the magical increment start values Matthew Auld
2017-11-24 21:29 ` [PATCH 3/9] x86/early-quirks: reverse the if ladders Matthew Auld
2017-11-24 21:29 ` [PATCH 4/9] drm/i915: nuke the duplicated stolen discovery Matthew Auld
2017-11-24 22:08 ` Chris Wilson
2017-11-24 21:29 ` [PATCH 5/9] drm/i915: s/mappable_end/mappable_size/ Matthew Auld
2017-11-24 22:11 ` Chris Wilson
2017-11-24 21:29 ` [PATCH 6/9] drm/i915: make dsm struct resource centric Matthew Auld
2017-11-24 22:15 ` Chris Wilson
2017-11-24 21:29 ` [PATCH 7/9] drm/i915: make reserved " Matthew Auld
2017-11-24 22:19 ` Chris Wilson
2017-11-24 21:29 ` [PATCH 8/9] drm/i915: make mappable " Matthew Auld
2017-11-24 22:22 ` Chris Wilson
2017-11-24 21:29 ` [PATCH 9/9] drm/i915: prefer resource_size_t for everything stolen Matthew Auld
2017-11-24 22:25 ` Chris Wilson
2017-11-24 21:50 ` ✓ Fi.CI.BAT: success for make stolen resource centric (rev3) Patchwork
2017-11-24 22:45 ` ✗ Fi.CI.IGT: warning " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-12-05 21:02 [PATCH 0/9] make stolen resource centric Matthew Auld
2017-12-05 21:02 ` [PATCH 1/9] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Matthew Auld
2017-12-07 12:28 [PATCH 0/9] make stolen resource centric Matthew Auld
2017-12-07 12:28 ` [PATCH 1/9] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Matthew Auld
2017-12-07 12:28 ` Matthew Auld
2017-12-08 22:58 ` Thomas Gleixner
2017-12-08 22:58 ` Thomas Gleixner
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=1511770293.4627.9.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--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=tglx@linutronix.de \
--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 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.