From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [CI 1/2] drm/i915/skl: Rework MOCS tables to keep common part in a define
Date: Fri, 30 Nov 2018 15:19:18 -0800 [thread overview]
Message-ID: <20181130231916.GA3330@ldmartin-desk.jf.intel.com> (raw)
In-Reply-To: <154361519380.20153.8174892913978589551@skylake-alporthouse-com>
On Fri, Nov 30, 2018 at 09:59:53PM +0000, Chris Wilson wrote:
> Quoting Lucas De Marchi (2018-11-30 21:33:03)
> > From: Tomasz Lis <tomasz.lis@intel.com>
> >
> > The MOCS tables are going to be very similar across platforms.
> >
> > To reduce the amount of copied code, this patch rips the common part and
> > puts it into a definition valid for all gen9 platforms.
> >
> > v2: Made defines for or-ing flags. Renamed macros from MOCS_TABLE
> > to MOCS_ENTRIES. (Joonas)
> >
> > Signed-off-by: Tomasz Lis <tomasz.lis@intel.com>
> > Suggested-by: Lucas De Marchi <lucas.demarchi@intel.com>
> > Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> (v1)
>
> Lucas, this needs your s-o-b if you are sending it for inclusion (to
> state that you do have the legal authority to do so).
Did I misunderstand the meaning of the CI tag? These are exactly the
same commits as https://patchwork.freedesktop.org/series/51258/
I'm only sending again to get them to run properly on CI since patchwork
got confused with the in-reply-to used there.
And I'm not going to apply these myself, so adding the s-o-b didn't seem
appropriate.
Lucas De Marchi
> -Chris
> _______________________________________________
> 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
next prev parent reply other threads:[~2018-11-30 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 21:33 [CI 1/2] drm/i915/skl: Rework MOCS tables to keep common part in a define Lucas De Marchi
2018-11-30 21:33 ` [CI 2/2] drm/i915/icl: Define MOCS table for Icelake Lucas De Marchi
2018-11-30 21:59 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915/skl: Rework MOCS tables to keep common part in a define Patchwork
2018-11-30 21:59 ` [CI 1/2] " Chris Wilson
2018-11-30 23:19 ` Lucas De Marchi [this message]
2018-11-30 23:35 ` Chris Wilson
2018-11-30 23:37 ` Chris Wilson
2018-11-30 23:47 ` Lucas De Marchi
2018-12-01 17:15 ` ✓ Fi.CI.IGT: success for series starting with [CI,1/2] " Patchwork
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=20181130231916.GA3330@ldmartin-desk.jf.intel.com \
--to=lucas.de.marchi@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
/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