[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20261105002520.GV23438@brightrain.aerifal.cx>
Date: Wed, 4 Nov 2026 19:25:20 -0500
From: Rich Felker <dalias@...c.org>
To: Imre Kaloz <kaloz@...nel.org>
Cc: musl@...ts.openwall.com
Subject: Re: [PATCH 00/10] add sparc64 port
On Wed, Nov 04, 2026 at 10:22:30PM +0100, Imre Kaloz wrote:
> On Wed, Nov 4, 2026, at 22:08, Rich Felker wrote:
> > On Mon, Nov 02, 2026 at 05:58:27PM +0100, Imre Kaloz wrote:
> >> This adds a sparc64 port.
> >
> > Before continuing with this, based on questions others have raised
> > with my thru other channels, I need to ask: is this in any way vibe
> > coded?
> >
> > That does not just include copying code verbatim out of a chatbot, but
> > using chatbot sessions to formulate the ideas of the code in any way.
>
> Not vibe coded, but AI reviewed if that matters. As sashiko is active now
> in almost every kernel list I submit patches to, I review all my work to
> avoid obvious mistakes if I can.
I'm not sure what that entails, but having changes made based on what
a model emitted when prompted with your original code counts. Please
do not do that and please inform us if you have.
Really there should be no "bot in the loop".
> P.S: I understand it's not perfect, but I hope you did not mean that the
> quality of it is as bad as it would have been vibe-coded
No, rather my understanding of the concern was that it was based on
having seen your work on LLVM target support, which clearly was.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
