All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Garg, Nemesa" <nemesa.garg@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: RE: [PATCH v2 1/2] drm/xe/compat: refactor compat i915_drv.h
Date: Fri, 07 Mar 2025 13:30:40 +0200	[thread overview]
Message-ID: <877c51hycf.fsf@intel.com> (raw)
In-Reply-To: <IA1PR11MB646726CF92026CD998153F89E3CA2@IA1PR11MB6467.namprd11.prod.outlook.com>

On Thu, 06 Mar 2025, "Garg, Nemesa" <nemesa.garg@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> @@ -0,0 +1,15 @@
>> +/* SPDX-License-Identifier: MIT */
>> +/* Copyright © 2025 Intel Corporation */
>> +
>> +#ifndef __I915_GEM_OBJECT_H__
>> +#define __i915_GEM_OBJECT_H__

Exceptionally, I took the liberty of fixing this while applying.

It was pure luck that I caught it with clang's -Wheader-guard [1].

[1] https://clang.llvm.org/docs/DiagnosticsReference.html#wheader-guard

> Reviewed-by: Nemesa Garg <nemesa.garg@intel.com>

Thanks for the review, series pushed to din.

BR,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-03-07 11:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 16:38 [PATCH v2 0/2] drm/xe/compat: cleanup Jani Nikula
2025-03-05 16:38 ` [PATCH v2 1/2] drm/xe/compat: refactor compat i915_drv.h Jani Nikula
2025-03-06  7:09   ` Garg, Nemesa
2025-03-07 11:30     ` Jani Nikula [this message]
2025-03-05 16:38 ` [PATCH v2 2/2] drm/i915/plane: convert intel_atomic_plane.[ch] to struct intel_display Jani Nikula
2025-03-06  5:39   ` Garg, Nemesa
2025-03-05 20:31 ` ✓ CI.Patch_applied: success for drm/xe/compat: cleanup Patchwork
2025-03-05 20:31 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-05 20:32 ` ✓ CI.KUnit: success " Patchwork
2025-03-05 20:48 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2025-03-05 20:48 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-03-05 20:49 ` ✓ CI.Build: success " Patchwork
2025-03-05 20:51 ` ✓ CI.Hooks: " Patchwork
2025-03-05 20:53 ` ✓ CI.checksparse: " Patchwork
2025-03-05 21:16 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-06  6:59 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-06 12:57 ` ✗ Fi.CI.BUILD: warning for drm/xe/compat: cleanup (rev2) Patchwork
2025-03-06 12:57 ` ✗ Fi.CI.CHECKPATCH: " Patchwork
2025-03-06 12:57 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-03-06 13:22 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-06 17:32 ` ✗ i915.CI.Full: failure " 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=877c51hycf.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=nemesa.garg@intel.com \
    --cc=rodrigo.vivi@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 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.