Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: igt-dev@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2 0/9] Start cleanup of local macros/structs
Date: Wed, 14 Jul 2021 14:04:27 -0700	[thread overview]
Message-ID: <87im1c4nfo.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <YO3u5irBRnR2F7uC@phenom.ffwll.local>

On Tue, 13 Jul 2021 12:52:06 -0700, Daniel Vetter wrote:
>
> On Sat, Jul 10, 2021 at 11:12:02PM -0700, Lucas De Marchi wrote:
> > We have a lot of LOCAL leftovers because:
> >
> > a) we needed a test before landing the kernel API, or
> > b) in the past we didn't copy the kernel headers, or
> > c) it's done everywhere, so people just copy and paste
> >
> > There are still some lingering in there, but this should cover the major
> > part.
>
> This is awesome, thanks for doing it. On the series.
>
> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>

For the series:

Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2021-07-14 21:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-11  6:12 [igt-dev] [PATCH i-g-t v2 0/9] Start cleanup of local macros/structs Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 1/9] include/drm-uapi: sync kernel headers Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 2/9] Remove local copies of I915 macros Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 3/9] tests/i915/gem_mmap_wc: drop LOCAL_IOCTL_I915_GEM_MMAP_v2 Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 4/9] lib/ioctl_wrappers: drop gem_require_stolen_support() Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 5/9] benchmarks/gem_exec_tracer: nuke LOCAL_IOCTL_I915_GEM_EXECBUFFER2_WR Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 6/9] benchmarks/gem_busy: nuke LOCAL_IOCTL_SYNCOBJ_CREATE Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 7/9] benchmarks/gem_busy: nuke LOCAL_IOCTL_SYNCOBJ_WAIT Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 8/9] Nuke local versions of DRM_FORMAT and DRM_MODE Lucas De Marchi
2021-07-11  6:12 ` [igt-dev] [PATCH i-g-t v2 9/9] tests/kms_sequence: nuke local drm definitions Lucas De Marchi
2021-07-11 13:34 ` [igt-dev] ✓ Fi.CI.BAT: success for Start cleanup of local macros/structs (rev2) Patchwork
2021-07-11 15:08 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-14 21:04   ` Dixit, Ashutosh
2021-07-14 23:51     ` Lucas De Marchi
2021-07-15 19:03       ` Lucas De Marchi
2021-07-13 19:52 ` [igt-dev] [PATCH i-g-t v2 0/9] Start cleanup of local macros/structs Daniel Vetter
2021-07-14 21:04   ` Dixit, Ashutosh [this message]
2021-07-15 13:36 ` [igt-dev] ✓ Fi.CI.BAT: success for Start cleanup of local macros/structs (rev3) Patchwork
2021-07-15 17:39 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=87im1c4nfo.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    /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