All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
	simona.vetter@ffwll.ch,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [git pull] drm for 6.15-rc1
Date: Tue, 01 Apr 2025 15:34:20 +0300	[thread overview]
Message-ID: <87r02c2h83.fsf@intel.com> (raw)
In-Reply-To: <CAHk-=wjMrqzuUmH-mFbR_46EWEFS=bB=J7h9ABMVy56Vi81PKQ@mail.gmail.com>

On Mon, 31 Mar 2025, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, 31 Mar 2025 at 03:17, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>>
>> I suggest a Kconfig knob to truly make this opt-in, only for developers
>> who actually want it.
>
> So honestly, the thing I *really* hated was the horrendous naming.
>
> I live in auto-complete. I basically never type out file-names, and I
> replace keyboards every once in a while because my TAB key has worn
> down (not really, but you get the idea).
>
> And *if* this feature is useful - and while I disagree about the whole
> "header files have to be self-sufficient" as a general rule, I can see
> it being useful for uapi headers - then dammit, the file naming needs
> to *DIE*. It needs to be taken out behind the shed and shot in the
> head, because it messes with TAB-completion.
>
> Having "this has been checked" turds that live in the same name-space
> as real files is wrong.
>
> In the kernel, we often hide them explicitly (ie using the dot prefix
> to make them hide, but also to make them not mess with auto-complete).
> That's an option. But some people hate the hiding, and if that's an
> issue, just put it all in a different subdirectory entirely.
>
> Yes, I realize that you guys may live in the whole "different
> subdirectory entirely" world of doing the whole build in a separate
> build directory, and might say "why are you working in the same tree
> as the generated files in the first place if auto-complete is so
> important to you".
>
> And to that I say "because I equally often look at the generated
> files". When they make *sense* to look at, not when they are
> auto-generated makefile checking crap.
>
> So please. This feature needs to be done completely differently.

I've polished, or, more accurately, hidden the disgusting turds [1]. I
hope this is an acceptable approach.

I've never claimed this feature is universally useful, certainly not for
all of include/linux, but I think it has been more helpful than not in
i915 and xe drivers. And now hopefully drm more widely. I wish kbuild
had support for it in a way that drivers could opt-in *if* they wanted
it, but without copy-pasting the boilerplate.


BR,
Jani.


[1] https://lore.kernel.org/r/20250401121830.21696-1-jani.nikula@intel.com


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-04-01 12:34 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
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 [this message]
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=87r02c2h83.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=simona.vetter@ffwll.ch \
    --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.