The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 "Kernel Mailing List, Linux" <linux-kernel@vger.kernel.org>,
	kvm <kvm@vger.kernel.org>,  Yosry Ahmed <yosry@kernel.org>
Subject: Re: [GIT PULL] KVM (mostly s390) fixes for Linux 7.2-rc7
Date: Fri, 7 Aug 2026 15:39:00 -0700	[thread overview]
Message-ID: <anZehP6yD66SRsNj@google.com> (raw)
In-Reply-To: <CABgObfak2WM10cj4eQ0DejFQPjsK1ftjS-y2Ygr_gcPs=KyChg@mail.gmail.com>

On Fri, Aug 07, 2026, Paolo Bonzini wrote:
> Il ven 7 ago 2026, 19:07 Sean Christopherson <seanjc@google.com> ha scritto:
> > On Fri, Aug 07, 2026, Paolo Bonzini wrote:
> > I don't care _that_ much about the code itself, though I still think the out-param
> > is all kinds of ugly. I'm not at all ok with doing so silently
> >
> > and without what I would consider an honest attempt to address review feedback.
> 
> Sorry about that, but again - I waited two weeks and got no reply to
> https://lore.kernel.org/all/CABgObfbDE+=ir_phPC+9sVYnNXur6dFx6oAfEGSnCbrOqFoyVA@mail.gmail.com/.
> I consider two weeks of wait, on a review that so far had been
> exclusively about taste, to *be* an honest attempt to gather the next
> round of feedback (which never came).

Heh, and I was waiting for a response to Yosry's thread:
https://lore.kernel.org/all/CAO9r8zODKgCcjTBK=P6BuXBBZRoOAFMeRJU8BmkWL-BCX2LoBw@mail.gmail.com

I also didn't prioritize responding (or even digging deeper) because I wasn't
expecting the patch to get fast-tracked to 7.2.  It's not tagged for stable, the
code has existed for years, and at least for me, nothing else suggested it needed
to go in *now*.  It doesn't help that the commit showed up in kvm/master late
yesterday; the first heads up I got that you were applying the patch as-is was
this pull request.

In other words, it's the lack of communication that's frustrating.  Even a simple
"Hey, I'm applying this unless someone screams" would have sufficed.

> If you had proposed the above small patch, for example, it would have
> been a completely different thing. 

Heh, if only past me had realized we could have done that.  I guess the desire to
prove someone "wrong" on the internet is the mother of all invention? :-D

> I would have taken your suggestion immediately.
> 
> Paolo
> 
> >
> > [1] https://lore.kernel.org/all/amPo-XdhFGIZquES@google.com
> > [2] https://lore.kernel.org/all/CAO9r8zM=Mb=eTEFGF0G-POvwwbSr7e8SN6zcDp=GstzKtBKcow@mail.gmail.com
> > [3] https://lore.kernel.org/all/CAO9r8zMopB=YKXs5pkQmPf9uHKE0P0XORcNbc60AWXTusuY3tg@mail.gmail.com
> >
> 

  reply	other threads:[~2026-08-07 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 13:53 [GIT PULL] KVM (mostly s390) fixes for Linux 7.2-rc7 Paolo Bonzini
2026-08-07 15:18 ` pr-tracker-bot
2026-08-07 17:06 ` Sean Christopherson
2026-08-07 21:41   ` Paolo Bonzini
2026-08-07 22:39     ` Sean Christopherson [this message]
2026-08-08  5:43       ` Paolo Bonzini

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=anZehP6yD66SRsNj@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yosry@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