From: Kees Cook <kees@kernel.org>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: Sabyrzhan Tasbolatov <snovitoll@gmail.com>,
Sasha Levin <sashal@kernel.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
rostedt@goodmis.org, konstantin@linuxfoundation.org,
corbet@lwn.net, josh@joshtriplett.org
Subject: Re: [RFC 0/2] Add AI coding assistant configuration to Linux kernel
Date: Sun, 27 Jul 2025 23:40:54 -0700 [thread overview]
Message-ID: <202507272336.E17C3032D@keescook> (raw)
In-Reply-To: <aIZJppabYBCDBhYJ@gallifrey>
On Sun, Jul 27, 2025 at 03:45:42PM +0000, Dr. David Alan Gilbert wrote:
> When doing qemu dev, I frequently run it in a tmux, and start it with
> '-nographic' which gets you a single stream with both serial and monitor in it;
> alternatively you can get one pane with the serial output and one with the
> monitor, that takes a little more setup;
Yeah, I haven't played with it yet, but I expect I'll need to try several
approaches and see which the agent can best deal with. It's better with
non-interactive stuff, so I'm thinking that giving it tooling that will
run a script at boot or have the image bring up ssh for the agent to run
individual commands via ssh... it all depends on what the agent can wrap
its logic around.
--
Kees Cook
next prev parent reply other threads:[~2025-07-28 6:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 9:37 [RFC 0/2] Add AI coding assistant configuration to Linux kernel Sabyrzhan Tasbolatov
2025-07-27 15:23 ` Kees Cook
2025-07-27 15:45 ` Dr. David Alan Gilbert
2025-07-28 6:40 ` Kees Cook [this message]
2025-07-28 16:43 ` Sabyrzhan Tasbolatov
-- strict thread matches above, loose matches on Subject: below --
2025-07-25 17:53 Sasha Levin
2025-07-25 18:41 ` Jakub Kicinski
2025-07-25 19:00 ` Steven Rostedt
2025-07-25 19:59 ` Jakub Kicinski
2025-07-25 20:32 ` Dr. David Alan Gilbert
2025-07-25 20:34 ` dan.j.williams
2025-07-25 22:28 ` Sasha Levin
2025-07-28 17:46 ` Steven Rostedt
2025-07-28 18:20 ` dan.j.williams
2025-07-28 22:12 ` Mauro Carvalho Chehab
2025-07-29 0:18 ` Mauro Carvalho Chehab
2025-07-25 21:03 ` Kees Cook
2025-07-28 15:57 ` dan.j.williams
2025-07-28 16:41 ` Kees Cook
2025-07-26 9:07 ` Mario Limonciello
2025-07-26 11:53 ` Sasha Levin
2025-07-26 16:36 ` Kees Cook
2025-07-28 16:49 ` Mauro Carvalho Chehab
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=202507272336.E17C3032D@keescook \
--to=kees@kernel.org \
--cc=corbet@lwn.net \
--cc=josh@joshtriplett.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=snovitoll@gmail.com \
--cc=workflows@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;
as well as URLs for NNTP newsgroup(s).