From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Klaus Jensen <its@irrelevant.dk>
Cc: Avi Kivity <avi@scylladb.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/nvme: add `model` parameter
Date: Fri, 6 Mar 2026 17:00:39 +0000 [thread overview]
Message-ID: <aasIN6T7aN8RhUfz@redhat.com> (raw)
In-Reply-To: <aal7cdCf2A0SUO_u@AALNPWKJENSEN.aal.scsc.local>
On Thu, Mar 05, 2026 at 01:47:45PM +0100, Klaus Jensen wrote:
> On Mar 5 13:11, Avi Kivity wrote:
> > On Mon, Mar 2, 2026 at 4:50 PM Avi Kivity <avi@scylladb.com> wrote:
> >
> > >
> > >
> > > On Mon, Mar 2, 2026 at 4:39 PM Daniel P. Berrangé <berrange@redhat.com>
> > > wrote:
> > >
> > >> On Mon, Mar 02, 2026 at 04:27:48PM +0200, Avi Kivity wrote:
> > >> > Add a `model` parameter, readable with nvme-cli. This allows
> > >> > impersonating other disk manufacturers or hypervisors, similar
> > >> > to the the -smbios option.
> > >> >
> > >> > Signed-off-by: Avi Kivity <avi@scylladb.com>
> > >> > ---
> > >> >
> > >> > Disclosure: prepared with AI assistance. I believe it to be of good
> > >> > quality.
> > >>
> > >> Can you clarify how AI was involved,
> > >
> > >
> > > I asked an LLM (Claude) to add a model parameter to the nvme code, which
> > > it did, then I asked it to documented it, which it also did.
> > >
> > >
> > >> as QEMU's policy is to decline
> > >> any contributions where AI was involing in an authoring role:
> > >>
> > >
> > > Very unfortunate. It would have taken me an hour or two to re-orient
> > > myself in the code base, for something that took me a couple of minutes
> > > with AI.
> > >
> >
> > So what's the verdict?
> >
> > FWIW I think the probability of AI copying these few lines from some
> > non-GPL project is zero.
>
> As maintainer I don't have a problem taking this patch, but I'm not sure
> how to deal with the policy in this instance.
When introducing the policy we had debated whether to allow so called
"trivial" patches where one might argue the copyrightability concerns
are negligible, but could not come to agreement on that matter so left
it as strict policy.
> Daniel, please advise if I can take this. I'd have written the patch
> like this myself.
To avoid having to exhaust time debating this, I've wrote new
patches myself without direct reference to Avi's proposal, which
do the equivalent thing, plus some more on top.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-03-06 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:27 [PATCH] hw/nvme: add `model` parameter Avi Kivity
2026-03-02 14:39 ` Daniel P. Berrangé
2026-03-02 14:50 ` Avi Kivity
2026-03-05 11:11 ` Avi Kivity
2026-03-05 12:47 ` Klaus Jensen
2026-03-06 17:00 ` Daniel P. Berrangé [this message]
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=aasIN6T7aN8RhUfz@redhat.com \
--to=berrange@redhat.com \
--cc=avi@scylladb.com \
--cc=its@irrelevant.dk \
--cc=qemu-devel@nongnu.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 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.