linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	 Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Arnd Bergmann <arnd@arndb.de>,
	Prasad Pandit <pjp@fedoraproject.org>,
	 Yang Li <yang.lee@linux.alibaba.com>
Subject: Re: [GIT PULL] tracing: Fixes for v6.9
Date: Fri, 12 Apr 2024 09:20:28 -0700	[thread overview]
Message-ID: <CAHk-=wj-hLLN_t_m5OL4dXLaxvXKy_axuoJYXif7iczbfgAevQ@mail.gmail.com> (raw)
In-Reply-To: <20240412121531.24669544@gandalf.local.home>

On Fri, 12 Apr 2024 at 09:15, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Note, the tab is here:

Yeah,  yeah, I checked.

I also checked that the normal "make defconfig" does not care.

In fact, I'm seriously inclined to make sure that our main Kconfig
file has several tabs in several places, just to make damn sure that
any broken sh*t is fixed.

Because no, the fix is *not* to try to fix invisible problems in the
Kconfig files themselves.

I've pulled your thing, but any parsers that think tabs and spaces are
different need to either be fixed, or they need to be shunned.

                     Linus

  parent reply	other threads:[~2024-04-12 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 14:32 [GIT PULL] tracing: Fixes for v6.9 Steven Rostedt
2024-04-12 16:07 ` Linus Torvalds
2024-04-12 16:15   ` Steven Rostedt
2024-04-12 16:20     ` Randy Dunlap
2024-04-12 16:21       ` Linus Torvalds
2024-04-12 16:29         ` Steven Rostedt
2024-04-12 16:20     ` Linus Torvalds [this message]
2024-04-12 16:08 ` 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='CAHk-=wj-hLLN_t_m5OL4dXLaxvXKy_axuoJYXif7iczbfgAevQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=pjp@fedoraproject.org \
    --cc=rostedt@goodmis.org \
    --cc=yang.lee@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).