Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Borislav Petkov <bp@alien8.de>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Joerg Roedel <joerg.roedel@amd.com>,
	"Nikunj A. Dadhania" <nikunj@amd.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: Removing __get_user / __put_user for good
Date: Wed, 21 Oct 2026 17:23:12 +0200	[thread overview]
Message-ID: <atjY4HV-OksEf0mf@gmail.com> (raw)
In-Reply-To: <CAHk-=wj51-syPoqMBLnxMeLnsbCMDMXfKzKZCtOHhwWEk5DeRw@mail.gmail.com>


* Linus Torvalds <torvalds@linuxfoundation.org> wrote:

> On Tue, 20 Oct 2026 at 11:10, Linus Torvalds
> <torvalds@linuxfoundation.org> wrote:
> >
> > And it all really does look obviously correct, but ...
> 
> I think I'm just gping to merge this. I don't love all the changes,
> but I love __get_user and __put_user less.

Good riddance in any case, and for the x86 bits:

	Acked-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

      parent reply	other threads:[~2026-10-21 15:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6ad07f8a.a0c71a5e.2d2efd.977a@mx.google.com>
     [not found] ` <20261018152358-mutt-send-email-mst@kernel.org>
     [not found]   ` <CAHk-=wiUn9EbV4TJ4J7OPY0fVc3UC+xb-pp=+rg3hRc4jQqihg@mail.gmail.com>
     [not found]     ` <20261018174250-mutt-send-email-mst@kernel.org>
     [not found]       ` <376ef9d0-b03f-4f85-aee5-46cf20eb00ae@gmail.com>
     [not found]         ` <20261020021924-mutt-send-email-mst@kernel.org>
     [not found]           ` <CAHk-=wjxtzD1TXZr5iWu0p1+Hu0YZP7jbNSwFkp7AJYmhzhVCA@mail.gmail.com>
2026-10-20  7:25             ` Removing __get_user / __put_user for good Linus Torvalds
2026-10-20  9:33               ` Jani Nikula
2026-10-21 16:36                 ` Rodrigo Vivi
2026-10-21 17:02                   ` Linus Torvalds
2026-10-20  9:46               ` Michael S. Tsirkin
2026-10-20 13:19               ` Ingo Molnar
2026-10-20 18:14                 ` Linus Torvalds
2026-10-20 21:10                   ` Linus Torvalds
2026-10-21  1:38                     ` Linus Torvalds
2026-10-21  2:54                       ` Borislav Petkov
2026-10-21  3:00                         ` Linus Torvalds
2026-10-21 18:43                           ` Borislav Petkov
2026-10-21 18:55                             ` Linus Torvalds
2026-10-21 20:11                               ` Borislav Petkov
2026-10-21 15:23                       ` Ingo Molnar [this message]

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=atjY4HV-OksEf0mf@gmail.com \
    --to=mingo@kernel.org \
    --cc=airlied@gmail.com \
    --cc=bp@alien8.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joerg.roedel@amd.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=mst@redhat.com \
    --cc=nikunj@amd.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.lendacky@amd.com \
    --cc=torvalds@linuxfoundation.org \
    --cc=tursulin@ursulin.net \
    --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