Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/2] drm/xe: Fix build with KUNIT=m
Date: Mon, 13 Nov 2023 17:04:26 +0200	[thread overview]
Message-ID: <87il65vgn9.fsf@intel.com> (raw)
In-Reply-To: <iqnwce72yngqs4uequb7s67q7aoesyxa2xcgxo6ungprj64b5u@ha5cyqpgq6oa>

On Mon, 13 Nov 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Mon, Nov 13, 2023 at 12:04:32PM +0200, Jani Nikula wrote:
>>On Thu, 09 Nov 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
>>> -	depends on DRM && PCI && MMU
>>> +	depends on DRM && PCI && MMU && (m || (y && KUNIT=y))
>>
>>What do plain m and y mean here?
>
> m == this config set to m
> y == this config set to y

Okay, TIL. Not a very common pattern.


-- 
Jani Nikula, Intel

  reply	other threads:[~2023-11-13 15:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 17:51 [Intel-xe] [PATCH 0/2] Fix builtin vs module configuration Lucas De Marchi
2023-11-09 17:51 ` [Intel-xe] [PATCH 1/2] fixup! drm/xe/display: Implement display support Lucas De Marchi
2023-11-09 18:58   ` Rodrigo Vivi
2023-11-09 17:51 ` [Intel-xe] [PATCH 2/2] drm/xe: Fix build with KUNIT=m Lucas De Marchi
2023-11-09 18:58   ` Rodrigo Vivi
2023-11-13 10:04   ` Jani Nikula
2023-11-13 13:47     ` Lucas De Marchi
2023-11-13 15:04       ` Jani Nikula [this message]
2023-11-09 20:57 ` [Intel-xe] ✓ CI.Patch_applied: success for Fix builtin vs module configuration Patchwork
2023-11-09 20:57 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-11-09 20:58 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-11-09 21:08 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-09 21:08 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-09 21:09 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-11-11 16:22 ` [Intel-xe] ✓ CI.Patch_applied: success for Fix builtin vs module configuration (rev2) Patchwork
2023-11-11 16:22 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-11-11 16:23 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-11-11 16:30 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-11 16:31 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-11 16:32 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-11-11 17:01 ` [Intel-xe] ✓ CI.BAT: " 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=87il65vgn9.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-xe@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