The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Gunnar Kudrjavets <gunnarku@amazon.com>
Cc: jbouron@amazon.com, jgg@ziepe.ca,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	noodles@meta.com, peterhuewe@gmx.de
Subject: Re: [PATCH] tpm: Remove dead NULL check in tpm2_flush_space()
Date: Sun, 10 May 2026 04:40:21 +0300	[thread overview]
Message-ID: <af_iBSYsCCxK4h2l@kernel.org> (raw)
In-Reply-To: <20260509225450.29027-1-gunnarku@amazon.com>

On Sat, May 09, 2026 at 10:54:49PM +0000, Gunnar Kudrjavets wrote:
> On Fri, May 09, 2026 at 11:28 AM Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > Just for sake of understanding:
> >
> > What is "kiro" and is assisted-by the tag supposed to be used here?
> 
> Kiro is an AI-powered IDE built on top of Claude [1]. In this case,
> it helped with reasoning about the correctness of the fix, generating
> test cases to validate the change, and formalizing the commit message.
> 
> I'm trying to follow the established guidelines for AI attribution
> in kernel contributions to maintain scientific integrity [2] ;-)

OK, cool. I do know what Claude is :-) Just was unfamiliar term.

> 
> On a more utopian note, it is likely that in a year or so there'll be
> research conducted into how AI-assisted development is influencing the
> changes to the kernel. My goal is to get into the habit of indicating
> that AI was used to increase the number of valid data points.

Sure.

> 
> [1] https://kiro.dev/
> [2] https://docs.kernel.org/process/coding-assistants.html
> 
> Gunnar

BR, Jarkko

  reply	other threads:[~2026-05-10  1:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260427163238.20230-1-gunnarku@amazon.com>
2026-05-09 11:28 ` [PATCH] tpm: Remove dead NULL check in tpm2_flush_space() Jarkko Sakkinen
2026-05-09 11:38   ` Jarkko Sakkinen
2026-05-09 22:54   ` Gunnar Kudrjavets
2026-05-10  1:40     ` Jarkko Sakkinen [this message]
     [not found] <e71c6d95-6c83-4fb4-8cd5-f66067fb68c5@molgen.mpg.de>
     [not found] ` <20260427225722.17878-1-gunnarku@amazon.com>
     [not found]   ` <531b82e9-46c6-485d-95e1-018a3e9fc1b6@molgen.mpg.de>
2026-05-09 12:26     ` Jarkko Sakkinen

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=af_iBSYsCCxK4h2l@kernel.org \
    --to=jarkko@kernel.org \
    --cc=gunnarku@amazon.com \
    --cc=jbouron@amazon.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noodles@meta.com \
    --cc=peterhuewe@gmx.de \
    /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