From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] sched/urgent for v6.16-rc7
Date: Thu, 21 Aug 2025 11:36:47 +0200 [thread overview]
Message-ID: <20250821093647.GN3245006@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAHk-=wiMNdBYJcDo47riSP5=_Re4A-itmBwBfsnDxZqvfn5tHQ@mail.gmail.com>
On Sun, Jul 20, 2025 at 11:20:31AM -0700, Linus Torvalds wrote:
> I've obviously pulled this, but considering that the thing isn't
> actually really an unsigned value in the first place, and all users
> seem to cast it to 'long' anyway, there's an obvious question... Why
> is it unsigned in the first place, rather than just make it be the
> more natural signed type?
Histerical raisins AFAIU. I think the original reason to make the thing
unsigned was to get the 2s complement wrapping behaviour.
Yes, these days we have -fwrapv and everybody knows signed types wrap
properly too (although Kees will argue signed should not wrap etc..).
But back then who knows.
next prev parent reply other threads:[~2025-08-21 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 12:04 [GIT pull] locking/urgent " Thomas Gleixner
2025-07-20 12:04 ` [GIT pull] sched/urgent " Thomas Gleixner
2025-07-20 18:20 ` Linus Torvalds
2025-08-21 9:36 ` Peter Zijlstra [this message]
2025-07-20 18:38 ` pr-tracker-bot
2025-07-20 12:05 ` [GIT pull] x86/urgent " Thomas Gleixner
2025-07-20 18:35 ` Linus Torvalds
2025-07-21 3:14 ` Ard Biesheuvel
2025-07-21 3:32 ` Linus Torvalds
2025-07-21 4:17 ` Ard Biesheuvel
2025-07-21 6:08 ` tglx
2025-07-21 6:25 ` Ard Biesheuvel
2025-07-20 18:38 ` pr-tracker-bot
2025-07-20 18:38 ` [GIT pull] locking/urgent " 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=20250821093647.GN3245006@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®