public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Antonio Argenziano <antonio.argenziano@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] lib/i915: Move mmap IOCTLs wrappers into separate file
Date: Tue, 26 Feb 2019 08:33:33 -0800	[thread overview]
Message-ID: <166a1abe-4ce7-6d2a-eac5-b5b56a475490@intel.com> (raw)
In-Reply-To: <20190226094927.GC4038@platvala-desk.ger.corp.intel.com>



On 26/02/19 01:49, Petri Latvala wrote:
> On Mon, Feb 25, 2019 at 04:20:19PM -0800, Antonio Argenziano wrote:
>> Move all mmap flavours and support function to separate file in i915
>> folder. This helps with moving i915 specific functions away from common
>> libraries.
>>
>> Signed-off-by: Antonio Argenziano <antonio.argenziano@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> ---
>>   lib/i915/gem_mman.c  | 254 +++++++++++++++++++++++++++++++++++++++++++
>>   lib/i915/gem_mman.h  |  55 ++++++++++
>>   lib/ioctl_wrappers.c | 213 ------------------------------------
>>   lib/ioctl_wrappers.h |  23 +---
>>   lib/meson.build      |   1 +
> 
> 
> Where's the change to lib/Makefile.sources?

Ops, I forgot about that.

Thanks,
Antonio

> 
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-02-26 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26  0:20 [igt-dev] [PATCH i-g-t 1/2] lib/i915: Move mmap IOCTLs wrappers into separate file Antonio Argenziano
2019-02-26  0:20 ` [igt-dev] [PATCH i-g-t 2/2] lib/i915: Add mmap_offset support Antonio Argenziano
2019-02-26  1:09 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/2] lib/i915: Move mmap IOCTLs wrappers into separate file Patchwork
2019-02-26  9:49 ` [igt-dev] [PATCH i-g-t 1/2] " Petri Latvala
2019-02-26 16:33   ` Antonio Argenziano [this message]
2019-02-26  9:54 ` Chris Wilson

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=166a1abe-4ce7-6d2a-eac5-b5b56a475490@intel.com \
    --to=antonio.argenziano@intel.com \
    --cc=igt-dev@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