From: Al Viro <viro@zeniv.linux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Ujwal Kundur <ujwal.kundur@gmail.com>,
allison.henderson@oracle.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rds: Fix endian annotations across various assignments
Date: Sun, 10 Aug 2025 20:26:12 +0100 [thread overview]
Message-ID: <20250810192612.GO222315@ZenIV> (raw)
In-Reply-To: <398e53d8-906d-43c9-9395-f6115dcb945b@lunn.ch>
On Sun, Aug 10, 2025 at 08:41:49PM +0200, Andrew Lunn wrote:
> This smells of an LLM generated patch.
Maybe, maybe not.
> So i think you are somewhat
> wasting your time explaining in detail why this is wrong. Well, maybe
> in a few generations of LLM it might learn from what you said, but
> that does not address the immediate problem.
You do realize that there _are_ humans out there, right? Ones capable of
learning, that is...
> We need developers using LLM to accept they have often wrong, and you
> need to spend time and effort:
>
> 1) Proving it got is wrong.
> 2) That after a lot of effort, failing to prove it wrong, accept it might be right.
> 3) Proving it actually got it right.
>
> It took me about 60 seconds to prove the POLLERR change was wrong, and
> i know nothing about this code base. So it is in fact not a lot of
> effort.
next prev parent reply other threads:[~2025-08-10 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 17:11 [PATCH net] rds: Fix endian annotations across various assignments Ujwal Kundur
2025-08-10 17:32 ` Andrew Lunn
2025-08-10 17:47 ` Al Viro
2025-08-10 18:25 ` Al Viro
2025-08-10 18:27 ` Al Viro
2025-08-10 18:41 ` Andrew Lunn
2025-08-10 19:26 ` Al Viro [this message]
2025-08-10 19:31 ` Ujwal Kundur
2025-08-10 20:19 ` Andrew Lunn
2025-08-10 21:00 ` Al Viro
2025-08-10 21:13 ` Al Viro
2025-08-10 18:38 ` Al Viro
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=20250810192612.GO222315@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=allison.henderson@oracle.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=ujwal.kundur@gmail.com \
/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.