lkmm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Szőke Benjamin" <egyszeregy@freemail.hu>
Cc: paulmck@kernel.org, stern@rowland.harvard.edu,
	parri.andrea@gmail.com,  will@kernel.org, peterz@infradead.org,
	boqun.feng@gmail.com,  npiggin@gmail.com, dhowells@redhat.com,
	j.alglave@ucl.ac.uk,  luc.maranget@inria.fr, akiyks@gmail.com,
	dlustig@nvidia.com,  joel@joelfernandes.org,
	linux-kernel@vger.kernel.org,  linux-arch@vger.kernel.org,
	lkmm@lists.linux.dev
Subject: Re: [PATCH] tools/memory-model: Fix litmus-tests's file names for case-insensitive filesystem.
Date: Mon, 11 Nov 2024 14:00:42 -0800	[thread overview]
Message-ID: <CAHk-=wiEuh613GjBefTRe-_Eha1X1GoU=1nLt65uccSBC8Ne=A@mail.gmail.com> (raw)
In-Reply-To: <a42da186-195c-40af-b4ee-0eaf6672cf2c@freemail.hu>

On Mon, 11 Nov 2024 at 13:15, Szőke Benjamin <egyszeregy@freemail.hu> wrote:
>
> There is a technical issue in the Linux kernel source tree's file naming/styles
> in git clone command on case-insensitive filesystem.

No.

This is entirely your problem.

The kernel build does not work, and is not intended to work on broken setups.

If you have a case-insensitive filesystem, you get to keep both broken parts.

I actively hate case-insensitive filesystems. It's a broken model in
so many ways. I will not lift a finger to try to help that
braindamaged setup.

"Here's a nickel, Kid. Go buy yourself a real computer"

             Linus

  parent reply	other threads:[~2024-11-11 22:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11 16:42 [PATCH] tools/memory-model: Fix litmus-tests's file names for case-insensitive filesystem egyszeregy
2024-11-11 16:54 ` Paul E. McKenney
2024-11-11 18:52   ` Szőke Benjamin
2024-11-11 19:22     ` Paul E. McKenney
2024-11-11 19:56       ` Szőke Benjamin
2024-11-11 20:29         ` Paul E. McKenney
2024-11-11 21:15           ` Szőke Benjamin
2024-11-11 21:23             ` Boqun Feng
2024-11-11 21:39               ` Szőke Benjamin
2024-11-11 21:44                 ` Boqun Feng
2024-11-11 21:52                 ` Paul E. McKenney
2024-11-11 22:00             ` Linus Torvalds [this message]
2024-11-11 23:21               ` Szőke Benjamin
2024-11-12  1:02                 ` Boqun Feng
2024-11-12 10:06                   ` Szőke Benjamin
2024-11-12 16:43                     ` Paul E. McKenney
2024-11-12 16:56                       ` Boqun Feng
2024-11-12  0:59             ` Alan Stern
2024-11-12  4:20               ` Paul E. McKenney
2024-11-12 15:35                 ` Alan Stern
2024-11-12 18:26                   ` Paul E. McKenney
2024-11-12 20:20                     ` Alan Stern
2024-11-12 21:53                       ` Paul E. McKenney
2024-12-12 23:09                         ` Szőke Benjamin

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-=wiEuh613GjBefTRe-_Eha1X1GoU=1nLt65uccSBC8Ne=A@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akiyks@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=egyszeregy@freemail.hu \
    --cc=j.alglave@ucl.ac.uk \
    --cc=joel@joelfernandes.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkmm@lists.linux.dev \
    --cc=luc.maranget@inria.fr \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --cc=will@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).