From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] core/entry for v6.6-rc1
Date: Mon, 28 Aug 2023 23:38:08 +0200 [thread overview]
Message-ID: <875y4y97b3.ffs@tglx> (raw)
In-Reply-To: <CAHk-=wjomZiu4QiyjAH=RSTsdZCpcjq-0yD42dLMN2+rcm4_cg@mail.gmail.com>
On Mon, Aug 28 2023 at 14:07, Linus Torvalds wrote:
> On Mon, 28 Aug 2023 at 06:01, Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>> A single update to the core entry code, which removes the empty user
>> address limit check which is a leftover of the removed TIF_FSCHECK.
>
> Heh. Lovely. I wonder if we have other cases of #ifdef's that just
> aren't #define'd anywhere any more.
I'm sure we have.
> But I'm too lazy and/or incompetent to write up some trivial script to check.
There are a few people out there who are constantly trying to chase
those:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/microcode&id=4d2b748305e96fb76202a0d1072a285b1500bff3
is the most recent example. But obviously they miss stuff too. :)
Thanks,
tglx
next prev parent reply other threads:[~2023-08-28 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 13:01 [GIT pull] core/entry for v6.6-rc1 Thomas Gleixner
2023-08-28 13:01 ` [GIT pull] irq/core " Thomas Gleixner
2023-08-28 22:15 ` pr-tracker-bot
2023-08-28 13:01 ` [GIT pull] smp/core " Thomas Gleixner
2023-08-28 22:15 ` pr-tracker-bot
2023-09-05 2:33 ` Michael Ellerman
2023-08-28 21:07 ` [GIT pull] core/entry " Linus Torvalds
2023-08-28 21:32 ` Linus Torvalds
2023-08-28 21:38 ` Thomas Gleixner [this message]
2023-08-28 22:15 ` 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=875y4y97b3.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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