intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, bp@suse.de, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/1] x86/gpu: Add Alderlake-S stolen memory support
Date: Tue, 26 Jan 2021 06:59:33 -0800	[thread overview]
Message-ID: <20210126145933.4qmwm7t3i3sotxmt@ldmartin-desk1> (raw)
In-Reply-To: <20210126102802.GB6514@zn.tnic>

On Tue, Jan 26, 2021 at 11:28:02AM +0100, Borislav Petkov wrote:
>On Mon, Jan 25, 2021 at 04:17:44PM -0800, Aditya Swarup wrote:
>> From: Caz Yokoyama <caz.yokoyama@intel.com>
>>
>> Alderlake-S is a Gen 12 based hybrid processor architecture. As it
>> belongs to Gen 12 family, it uses the same GTT stolen memory settings
>> like its predecessors - ICL(Gen 11) and TGL(Gen 12). Inherit gen11
>> and gen 9 quirks for determining base and size of stolen memory.
>>
>> v2: Fix typos in commit message.(Boris Petkov)
>
>For the future: patch changelog information goes...
>
>> Bspec: 52055
>> Bspec: 49589
>> Bspec: 49636
>>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Cc: x86@kernel.org
>> Cc: Ingo Molnar <mingo@redhat.com>,
>> Cc: Thomas Gleixner <tglx@linutronix.de>,
>> Cc: Borislav Petkov <bp@suse.de>
>> Signed-off-by: Caz Yokoyama <caz.yokoyama@intel.com>
>> Signed-off-by: Aditya Swarup <aditya.swarup@intel.com>
>> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>> ---
>
><--- ... here, under those lines. But no need to resend now, I believe
>the committer of this will fix it up.
>
>Acked-by: Borislav Petkov <bp@suse.de>

Thanks, I fixed that up and applied to drm-intel topic/adl-s-enabling
branch.

Lucas De Marchi

>
>Thx.
>
>-- 
>Regards/Gruss,
>    Boris.
>
>https://people.kernel.org/tglx/notes-about-netiquette
>_______________________________________________
>Intel-gfx mailing list
>Intel-gfx@lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-01-26 14:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  0:17 [Intel-gfx] [PATCH 0/1] Add Alderlake-S stolen memory changes Aditya Swarup
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 [this message]
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
2021-01-25 10:59 ` [Intel-gfx] [PATCH 1/1] x86/gpu: Add Alderlake-S stolen memory support Aditya Swarup
2021-01-25 17:33   ` Borislav Petkov

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=20210126145933.4qmwm7t3i3sotxmt@ldmartin-desk1 \
    --to=lucas.demarchi@intel.com \
    --cc=bp@alien8.de \
    --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).