From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
intel-gfx@lists.freedesktop.org, x86@kernel.org,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 1/2] x86/gpu: reserve ICL's graphics stolen memory
Date: Thu, 5 Jul 2018 07:52:28 -0700 [thread overview]
Message-ID: <20180705145228.GG734@intel.com> (raw)
In-Reply-To: <20180704055041.GA29478@gmail.com>
On Wed, Jul 04, 2018 at 07:50:42AM +0200, Ingo Molnar wrote:
>
> * Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
>
> > > Cc: Thomas Gleixner <tglx@linutronix.de>
> > > > > > Cc: Ingo Molnar <mingo@kernel.org>
> > > > > > Cc: H. Peter Anvin <hpa@zytor.com>
> > > > > > Cc: x86@kernel.org
> > >
> > > guys, could we push this through drm-intel? ack?
> > > nack? comments?
> >
> > Is there any concern with this patch?
> > any ack for push this through drm-intel?
> > or any nack with explanations please?
> >
> > I'd like to push this for 4.19 because this is
> > one of the patches that blocks us on using drm-tip
> > on ICL.
>
> Sorry - no objections, and I suppose it will be all tested properly before going
> upstream:
np. yeap, we have that running on ICLs here with internal branch for a while already.
>
> Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Rodrigo.
>
> Thanks,
>
> Ingo
next prev parent reply other threads:[~2018-07-05 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180503002352.11951-1-paulo.r.zanoni@intel.com>
2018-05-04 20:32 ` [PATCH 1/2] x86/gpu: reserve ICL's graphics stolen memory Paulo Zanoni
2018-05-07 8:46 ` Joonas Lahtinen
2018-06-01 21:44 ` Paulo Zanoni
2018-06-18 17:47 ` [Intel-gfx] " Rodrigo Vivi
2018-07-03 19:11 ` Rodrigo Vivi
2018-07-04 5:50 ` Ingo Molnar
2018-07-05 14:52 ` Rodrigo Vivi [this message]
2018-07-10 23:40 ` Rodrigo Vivi
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=20180705145228.GG734@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulo.r.zanoni@intel.com \
--cc=stable@vger.kernel.org \
--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 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).