From: Jeff McGee <jeff.mcgee@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, beignet@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t v3] tests/core_getparams: Create new test core_getparams
Date: Fri, 13 Mar 2015 10:03:44 -0700 [thread overview]
Message-ID: <20150313170344.GM3263@jeffdesk> (raw)
In-Reply-To: <20150313165913.GI3800@phenom.ffwll.local>
On Fri, Mar 13, 2015 at 05:59:13PM +0100, Daniel Vetter wrote:
> On Fri, Mar 13, 2015 at 09:51:57AM -0700, Jeff McGee wrote:
> > On Fri, Mar 13, 2015 at 05:32:41PM +0100, Daniel Vetter wrote:
> > > On Fri, Mar 13, 2015 at 05:09:46PM +0800, Zhigang Gong wrote:
> > > > My only concern is about the following macros:
> > > >
> > > > > +#define LOCAL_I915_PARAM_SUBSLICE_TOTAL 33
> > > > > +#define LOCAL_I915_PARAM_EU_TOTAL 34
> > > >
> > > > How about to just use the definitons in the kernel header file?
> > > > For an example:
> > > >
> > > > #include <drm/i915_drm.h>
> > > >
> > > > #ifdef LOCAL_I915_PARAM_SUBSLICE_TOTAL
> > > > //Put all the code into this block.
> > > > #endif
> > > >
> > > > Then we can avoid put the same definitions in different files,
> > > > and we can avoid unecessary testing on an old kernel which doesn't
> > > > have this kernel interface.
> > > >
> > > > For all the other part, it LGTM.
> > > >
> > > > Reviewed-by: Zhigang Gong <zhigang.gong@linux.intel.com>
> > >
> > > Once we update the libdrm requirements in igt we tend to go around and
> > > replace all the now obsolete LOCAL_ defines. Imo not worth doing extra
> > > work until then.
> > >
> > > Patch applied, thanks.
> > > -Daniel
> > >
> >
> > Patch applied? Do you want me to make the name change first? Should the
> > kernel part be reviewed and merged first?
>
> Forgot my own review comment already ;-) Fixed up with a follow-up patch.
> And I'll pull the kernel part in now too.
> -Daniel
Thanks. That leaves just the libdrm patch and version bump before Beignet
can merge their patches.
-Jeff
_______________________________________________
Beignet mailing list
Beignet@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/beignet
prev parent reply other threads:[~2015-03-13 17:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 23:40 [PATCH] tests/core_getparams: Create new test core_getparams jeff.mcgee
2015-03-09 23:19 ` [PATCH i-g-t 1/2] " jeff.mcgee
2015-03-09 23:19 ` [PATCH i-g-t 2/2] configure: Bump required libdrm version to 2.4.60 jeff.mcgee
2015-03-09 23:30 ` jeff.mcgee
2015-03-09 23:41 ` jeff.mcgee
2015-03-10 7:37 ` [Intel-gfx] " Daniel Vetter
2015-03-10 16:59 ` [Beignet] " Jeff McGee
2015-03-10 17:58 ` Rob Clark
2015-03-10 18:34 ` Jeff McGee
2015-03-10 18:24 ` [Beignet] " Rob Clark
2015-03-10 18:47 ` [Intel-gfx] " Daniel Vetter
2015-03-10 20:06 ` Jeff McGee
2015-03-11 7:21 ` Daniel Vetter
2015-03-12 20:42 ` [Beignet] " Jeff McGee
2015-03-12 20:38 ` [PATCH i-g-t v2] tests/core_getparams: Create new test core_getparams jeff.mcgee
2015-03-13 0:26 ` [PATCH i-g-t v3] " jeff.mcgee
2015-03-13 8:58 ` Daniel Vetter
2015-03-13 9:09 ` [Intel-gfx] " Zhigang Gong
2015-03-13 16:32 ` Daniel Vetter
2015-03-13 16:51 ` [Beignet] [Intel-gfx] " Jeff McGee
2015-03-13 16:59 ` [Beignet] " Daniel Vetter
2015-03-13 17:03 ` Jeff McGee [this message]
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=20150313170344.GM3263@jeffdesk \
--to=jeff.mcgee@intel.com \
--cc=beignet@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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).