From: Peter Zijlstra <peterz@infradead.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Christian <servidorjarvis1@gmail.com>,
dave.hansen@linux.intel.com, luto@kernel.org, tglx@kernel.org,
mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] x86/mm/pat: HIGHMEM pages in set_pages_array_*()
Date: Fri, 20 Nov 2026 18:07:32 +0100 [thread overview]
Message-ID: <20261120170732.GT2668804@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <3203b72a-6585-4f65-8eec-a17881ebd76e@intel.com>
On Fri, Nov 20, 2026 at 09:04:29AM -0800, Dave Hansen wrote:
> On 11/20/26 08:45, Christian wrote:
> > About the AI part: English is not my first language (I'm from Spain),
> > and I mostly use AI tools to translate between Spanish and English. The
> > work itself is mine. I found this bug on my own tablet, I traced it
> > myself, and I'm going through it one step at a time. And yes, I'll be
> > around. If this breaks something, I'll help fix it.
>
> I've heard this exact explanation from two different contributors in the
> past 24 hours alone.
>
> All of you were only constrained by your language skills from making
> kernel contributions? Then, suddenly, LLMs got good enough at
> _translation_ to make these contributions possible? While at the same
> time LLMs were getting orders of magnitude better at coding?
>
> I'm skeptical. Do you blame me?
Notably, things like Google-Translate have been good enough to translate
'simple' text for a good while now. And we have definitely seen people
use translation tools before this LLM onslaught started.
prev parent reply other threads:[~2026-11-20 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 9:49 Christian
2026-11-17 9:49 ` [PATCH 1/2] x86/mm/pat: skip HIGHMEM pages in a page array Christian
2026-11-17 9:49 ` [PATCH 2/2] x86/mm/pat: track the memory type of " Christian
2026-11-19 19:45 ` [PATCH 0/2] x86/mm/pat: HIGHMEM pages in set_pages_array_*() Dave Hansen
2026-11-20 7:50 ` Christian
2026-11-20 15:13 ` Dave Hansen
2026-11-20 16:45 ` Christian
2026-11-20 17:04 ` Dave Hansen
2026-11-20 17:07 ` Peter Zijlstra [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=20261120170732.GT2668804@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=servidorjarvis1@gmail.com \
--cc=tglx@kernel.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®