public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] intel: Add I915_PARAM_HAS_ATOMICS.
Date: Thu, 3 Oct 2013 09:32:36 +0200	[thread overview]
Message-ID: <20131003073235.GC31334@phenom.ffwll.local> (raw)
In-Reply-To: <20131002223225.GB6580@bwidawsk.net>

On Wed, Oct 02, 2013 at 03:32:25PM -0700, Ben Widawsky wrote:
> On Wed, Oct 02, 2013 at 03:06:00PM -0700, Francisco Jerez wrote:
> > Signed-off-by: Francisco Jerez <currojerez@riseup.net>
> > ---
> >  include/drm/i915_drm.h | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/include/drm/i915_drm.h b/include/drm/i915_drm.h
> > index f3be97a..d2a1018 100644
> > --- a/include/drm/i915_drm.h
> > +++ b/include/drm/i915_drm.h
> > @@ -311,6 +311,7 @@ typedef struct drm_i915_irq_wait {
> >  #define I915_PARAM_HAS_EXEC_NO_RELOC	 25
> >  #define I915_PARAM_HAS_EXEC_HANDLE_LUT   26
> >  #define I915_PARAM_HAS_WT     	 	 27
> > +#define I915_PARAM_HAS_ATOMICS           28
> >  
> >  typedef struct drm_i915_getparam {
> >  	int param;
> 
> Both of these look fine to me. I thought we had a more automated way of
> doing this, though I cannot recall.
> 
> Acked-by: Ben Widawsky <ben@bwidawsk.net>

make headers_install + copy it to libdrm + git commit is the most
automated way ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2013-10-03  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 22:05 [PATCH 1/2] intel: Update param definitions from the kernel headers Francisco Jerez
2013-10-02 22:06 ` [PATCH 2/2] intel: Add I915_PARAM_HAS_ATOMICS Francisco Jerez
2013-10-02 22:32   ` Ben Widawsky
2013-10-03  7:32     ` Daniel Vetter [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=20131003073235.GC31334@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=ben@bwidawsk.net \
    --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