From: Peter Zijlstra <peterz@infradead.org>
To: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, rafael@kernel.org, viresh.kumar@linaro.org,
mathieu.desnoyers@efficios.com, paulmck@kernel.org,
hannes@cmpxchg.org, surenb@google.com
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH] sched: Make clangd usable
Date: Fri, 23 May 2025 18:49:14 +0200 [thread overview]
Message-ID: <20250523164914.GO39944@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250523164348.GN39944@noisy.programming.kicks-ass.net>
On Fri, May 23, 2025 at 06:43:48PM +0200, Peter Zijlstra wrote:
>
> Due to the weird Makefile setup of sched the various files do not
> compile as stand alone units. The new generation of editors are trying
> to do just this -- mostly to offer fancy things like completions but
> also better syntax highlighting and code navigation.
To be fair, by far the biggest help has turned out to be to get instant
compiler warning/fails while you type code. This has drastically reduced
the stupid typo, doesn't compile, try again cycle.
Code completion is 'cute' but I'm not really limited in typing speed,
getting pop-up function arguments while typing is useful.
The better code navigation is also very useful.
next prev parent reply other threads:[~2025-05-23 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 16:43 [PATCH] sched: Make clangd usable Peter Zijlstra
2025-05-23 16:48 ` Tejun Heo
2025-05-23 18:19 ` Tejun Heo
2025-05-23 21:02 ` Andrea Righi
2025-05-23 16:49 ` Peter Zijlstra [this message]
2025-05-23 18:09 ` Steven Rostedt
2025-05-26 7:41 ` Peter Zijlstra
2025-05-26 8:11 ` Ingo Molnar
2025-05-26 8:59 ` Peter Zijlstra
2025-05-26 9:04 ` Peter Zijlstra
2025-05-26 11:44 ` Peter Zijlstra
2025-05-26 14:49 ` Juri Lelli
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=20250523164914.GO39944@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vschneid@redhat.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