From: Jonathan Corbet <corbet@lwn.net>
To: Eli Billauer <eli.billauer@gmail.com>, gregkh@linuxfoundation.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Eli Billauer <eli.billauer@gmail.com>
Subject: Re: [PATCH v2 0/7] char: xillybus: Harden driver and improve code quality
Date: Wed, 22 Jul 2026 08:49:35 -0600 [thread overview]
Message-ID: <87o6fzdqps.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260722102307.49090-1-eli.billauer@gmail.com>
Eli Billauer <eli.billauer@gmail.com> writes:
> This patch set consists of several boundary and sanity checks, gaining
> better control of execution flow and fixing minor coding issues. No
> difference is expected in the driver's behavior under normal conditions,
> except for one change that might improve bandwidth performance
> marginally.
>
> These patches are the result of a comprehensive AI-assisted code review,
> using Deepseek, Kimi Thinking K2.6, ChatGPT, and Claude Sonnet 4.6 as
> plain prompt tools.
So it would seem that they need Assisted-by tags?
Thanks,
jon
next prev parent reply other threads:[~2026-07-22 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 10:23 Eli Billauer
2026-07-22 10:23 ` [PATCH v2 1/7] char: xillybus: Improve control of execution flow with mutexes Eli Billauer
2026-07-22 10:23 ` [PATCH v2 2/7] char: xillybus: Remove duplicate error path code Eli Billauer
2026-07-22 10:23 ` [PATCH v2 3/7] char: xillybus: Avoid possible bandwidth inefficiency Eli Billauer
2026-07-22 10:23 ` [PATCH v2 4/7] char: xillybus: Use unsigned arithmetic for jiffies differences Eli Billauer
2026-07-22 10:23 ` [PATCH v2 5/7] char: xillybus: Integer arithmetic improvements Eli Billauer
2026-07-22 10:23 ` [PATCH v2 6/7] char: xillybus: Add defensive sanity checks Eli Billauer
2026-07-22 10:23 ` [PATCH v2 7/7] char: xillybus: Ignore and report unsolicited interrupts Eli Billauer
2026-07-22 14:49 ` Jonathan Corbet [this message]
2026-07-22 15:53 ` [PATCH v2 0/7] char: xillybus: Harden driver and improve code quality Eli Billauer
2026-07-22 16:00 ` Greg KH
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=87o6fzdqps.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=arnd@arndb.de \
--cc=eli.billauer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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®