All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>, Masahiro Yamada <masahiroy@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Airlie <airlied@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 6.15-rc1
Date: Tue, 01 Apr 2025 22:42:35 +0300	[thread overview]
Message-ID: <877c433bys.fsf@intel.com> (raw)
In-Reply-To: <20250401191455.GC325917@nvidia.com>

On Tue, 01 Apr 2025, Jason Gunthorpe <jgg@nvidia.com> wrote:
> So, I'd suggest a better way to run this is first build the kernel,
> then mine the gcc -MD output (ie stored in the .XX.cmd files) to
> generate a list of headers that are actually part of the build, then
> only test those. That eliminates all the kconfig problems. Opt out any
> special headers that really have a good reason not to be stand alone.

I think we'd want the drm headers pass the checks independent of configs
(apart from CONFIG_DRM). One size doesn't fit all.

BR,
Jani.


-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-04-01 19:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  2:53 [git pull] drm for 6.15-rc1 Dave Airlie
2025-03-29  0:47 ` Linus Torvalds
2025-03-31 10:17   ` Jani Nikula
2025-03-31 11:03     ` Simona Vetter
2025-03-31 13:31       ` Jason Gunthorpe
2025-04-01 12:21         ` Jani Nikula
2025-04-01 16:12           ` Linus Torvalds
2025-04-01 18:46             ` Masahiro Yamada
2025-04-01 19:14               ` Jason Gunthorpe
2025-04-01 19:36                 ` Masahiro Yamada
2025-04-01 19:42                 ` Jani Nikula [this message]
2025-04-01 19:46                   ` Jason Gunthorpe
2025-04-02 12:56                     ` Jani Nikula
2025-04-02 13:03                       ` Jason Gunthorpe
2025-04-02 13:53                         ` Jani Nikula
2025-04-02 14:41                           ` Simona Vetter
2025-04-02 16:34                             ` Jason Gunthorpe
2025-04-01 19:28               ` Jani Nikula
2025-03-31 15:42     ` Linus Torvalds
2025-04-01 12:34       ` Jani Nikula
2025-03-29  1:01 ` pr-tracker-bot

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=877c433bys.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jgg@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@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 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.