public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 6.10-rc1
Date: Thu, 16 May 2024 11:04:40 +0300	[thread overview]
Message-ID: <87v83eb2sn.fsf@intel.com> (raw)
In-Reply-To: <CAHk-=whuCX-NAGOLzwn5sObPDJX-pdqamZ7YTpHFHODAMv4P+A@mail.gmail.com>

On Wed, 15 May 2024, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, 15 May 2024 at 16:17, Dave Airlie <airlied@gmail.com> wrote:
>> AMDGPU, I915 and XE all have !COMPILE_TEST on their variants
>
> Hmm.  It turns out that I didn't notice the AMDGPU one because my
> Threadripper - that has AMDGPU enabled - I have actually turned off
> EXPERT on, so it's hidden by that for me.
>
> But yes, both of those should be "depends on !WERROR" too.

Fair enough. Honestly it just didn't occur to me.

The main goal here was to ensure the drm subsystem does not have any
build warnings, but without halting CI on any non-drm warnings that
might occasionally creep in and that we can't fix as quickly.

If there was a way to somehow limit WERROR by subdirectories, without
config options, I'd love to ditch the config.

> Or maybe they should just go away entirely, and be subsumed by the
> DRM_WERROR thing.

For i915, this was the idea anyway, we just haven't gotten around to it
yet.


BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2024-05-16  8:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  6:20 [git pull] drm for 6.10-rc1 Dave Airlie
2024-05-15 17:20 ` pr-tracker-bot
2024-05-15 20:06 ` Linus Torvalds
2024-05-15 20:21   ` Linus Torvalds
2024-05-15 20:24     ` Linus Torvalds
2024-05-15 20:29       ` Linus Torvalds
2024-05-15 23:50         ` Dave Airlie
2024-05-16  0:06           ` Dave Airlie
2024-05-16  2:42             ` Dave Airlie
2024-05-16  6:23               ` Paneer Selvam, Arunpravin
2024-05-15 23:51         ` Dave Airlie
2024-05-16  0:05           ` Linus Torvalds
2024-05-15 20:43 ` Linus Torvalds
2024-05-15 22:45   ` Dave Airlie
2024-05-15 22:56     ` Linus Torvalds
2024-05-15 23:17       ` Dave Airlie
2024-05-15 23:58         ` Linus Torvalds
2024-05-16  8:04           ` Jani Nikula [this message]
2024-05-16 13:04             ` Alex Deucher
2024-05-16 14:22         ` Sean Christopherson

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=87v83eb2sn.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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