All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCHv3 i-g-t] lib: substitute cxt BAN_PERIOD with BANNABLE
Date: Fri, 11 Nov 2016 16:36:08 +0200	[thread overview]
Message-ID: <87mvh65bjb.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20161111140523.GW9300@nuc-i3427.alporthouse.com>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> On Fri, Nov 11, 2016 at 03:55:03PM +0200, Mika Kuoppala wrote:
>> Context BAN_PERIOD will get depracated so subsitute it with BANNABLE
>> property. Make ctx param test to accept both variants for now
>> until kernel changes have landed, to not break BAT.
>> 
>> v2: check against - EINVAL on get/set ban as it can return -EPERM
>> v3: better naming for get/set (Chris)
>> 
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> There's a small assumption of symmetry between the get/set paths, but it
> looks ok as a transitional patch.
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Pushed. Thanks for review.

-Mika


> -Chris
>
> -- 
> Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-11-11 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 17:31 [PATCH i-g-t] lib: substitute cxt BAN_PERIOD with BANNABLE Mika Kuoppala
2016-11-11 13:01 ` Mika Kuoppala
2016-11-11 13:55 ` [PATCHv3 " Mika Kuoppala
2016-11-11 14:05   ` Chris Wilson
2016-11-11 14:36     ` Mika Kuoppala [this message]
2016-11-11 14:07   ` Mika Kuoppala

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=87mvh65bjb.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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.