From: Aditya Swarup <aditya.swarup@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: bp@suse.de, x86@kernel.org
Subject: [Intel-gfx] [PATCH 0/1] Add Alderlake-S stolen memory changes.
Date: Mon, 25 Jan 2021 16:17:43 -0800 [thread overview]
Message-ID: <20210126001744.29442-1-aditya.swarup@intel.com> (raw)
Based on Borislav Petkov's feedback, fix commit message so that it
describes the change properly.
Bspec is an Intel specific programming spec and as such drm/i915 patches
filtering in from Intel branches like drm-intel contain this information.
For example commit:
693260cf23f9 drm/i915/rkl: Add new cdclk table
It helps in tagging commits with spec changes as there might be updates
or provides info to the person trying to fix an issue arising from the
commit.
This patch has already been reviewed and needs an ack from x86/gpu
maintainers.
Note that this patch depends on commit 0883d63b19bb
("drm/i915/adl_s: Add ADL-S platform info and PCI ids")
Cc: Borislav Petkov <bp@suse.de>
Cc: x86@kernel.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Caz Yokoyama (1):
x86/gpu: Add Alderlake-S stolen memory support
arch/x86/kernel/early-quirks.c | 1 +
1 file changed, 1 insertion(+)
--
2.27.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-01-26 0:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 0:17 Aditya Swarup [this message]
2021-01-26 0:17 ` [Intel-gfx] [PATCH 1/1] x86/gpu: Add Alderlake-S stolen memory support Aditya Swarup
2021-01-26 10:28 ` Borislav Petkov
2021-01-26 14:59 ` Lucas De Marchi
2021-01-26 2:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add Alderlake-S stolen memory changes Patchwork
2021-01-26 3:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-26 10:10 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-01-25 10:59 [Intel-gfx] [PATCH 0/1] " Aditya Swarup
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=20210126001744.29442-1-aditya.swarup@intel.com \
--to=aditya.swarup@intel.com \
--cc=bp@suse.de \
--cc=intel-gfx@lists.freedesktop.org \
--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).