From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL] x86/mm changes for v6.8
Date: Tue, 9 Jan 2024 09:34:29 +0100 [thread overview]
Message-ID: <ZZ0FFWqSFthvi03V@gmail.com> (raw)
In-Reply-To: <CAHk-=wiOJOOyWvZOUsKppD068H3D=5dzQOJv5j2DU4rDPsJBBg@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, 8 Jan 2024 at 18:06, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > This does not even compile for me.
> >
> > arch/x86/include/asm/uaccess_64.h: In function ‘__untagged_addr’:
> > arch/x86/include/asm/uaccess_64.h:25:28: error: implicit declaration
> > of function ‘__my_cpu_var’; did you mean ‘put_cpu_var’?
> > [-Werror=implicit-function-declaration]
>
> Side note: the whole __my_cpu_var() reminds me of the attached patch
> that I have in my testing tree, and have been carrying along for a
> number of months now.
>
> I definitely think it's the right thing to do, so here it is again,
Yeah, that's a good patch I have queued up in tip:x86/percpu:
24b8a23638cb ("x86/fpu: Clean up FPU switching in the middle of task switching")
Merged it shortly after you sent it:
commit 24b8a23638cbf92449c353f828b1d309548c78f4
Author: Linus Torvalds <torvalds@linux-foundation.org>
AuthorDate: Wed Oct 18 20:41:58 2023 +0200
Commit: Ingo Molnar <mingo@kernel.org>
CommitDate: Fri Oct 20 11:24:22 2023 +0200
I planned to send an RFC pull request for these bits in this merge window,
after all the other x86 trees.
Thanks,
Ingo
next prev parent reply other threads:[~2024-01-09 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 11:35 [GIT PULL] x86/mm changes for v6.8 Ingo Molnar
2024-01-09 2:06 ` Linus Torvalds
2024-01-09 3:57 ` Linus Torvalds
2024-01-09 8:34 ` Ingo Molnar [this message]
2024-01-09 8:28 ` Ingo Molnar
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=ZZ0FFWqSFthvi03V@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.