All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] intel: merge latest i915_drm.h
Date: Mon, 14 Dec 2015 09:34:55 +0100	[thread overview]
Message-ID: <20151214083455.GC3189@phenom.ffwll.local> (raw)
In-Reply-To: <CACvgo50ZGukAsd7X=bb6mKVO_7s3PJ1g4fS6fAvY1iGZ+hvUcg@mail.gmail.com>

On Sat, Dec 12, 2015 at 03:16:59PM +0000, Emil Velikov wrote:
> On 11 December 2015 at 21:55, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > Pick up context flags, softpin, etc.
> >
> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> > ---
> >  include/drm/i915_drm.h | 57 ++++++++++++++++++++++++++++++++++++++++++--------
> >  1 file changed, 48 insertions(+), 9 deletions(-)
> >
> Any objections if we do this (and pretty much every other outdated
> header) in a single go, as the header cleanups hit Linus' tree ?
> Dave already has then in drm-next :-)

Ack. Maybe we should just script this and update before doing a libdrm
release in general? Updating from drm-next should never result in broken
ABI.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2015-12-14  8:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 21:55 [PATCH] intel: merge latest i915_drm.h Jesse Barnes
2015-12-12 15:16 ` Emil Velikov
2015-12-12 22:23   ` Jesse Barnes
2015-12-14  8:34   ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-04 22:59 [PATCH] i915: Add I915_PARAM_REVISION Emil Velikov
2015-03-05 14:11 ` [PATCH] intel: Merge latest i915_drm.h Neil Roberts

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=20151214083455.GC3189@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.