qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Leonardo Bras Soares Passos <leobras@redhat.com>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Juan Quintela <quintela@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/1] pcie: Add hotplug detect state register to cmask
Date: Thu, 6 Jul 2023 16:17:20 -0400	[thread overview]
Message-ID: <ZKchUNPG1mofzSOC@x1n> (raw)
In-Reply-To: <20230706155936-mutt-send-email-mst@kernel.org>

On Thu, Jul 06, 2023 at 04:00:49PM -0400, Michael S. Tsirkin wrote:
> I mean his patch is exactly right. cmask was designed with this
> kind of use case in mind.
> Will queue.

That's great news.

> If you want to suggest more text to the commit log, for the benefit
> of backporters, that is fine by me.

If you're fine with it I've no issue; since we're reaching soft-freeze I'd
think it better if it can be merged on time (or just slightly enhance the
commit message when merge).

Thanks!

-- 
Peter Xu



  reply	other threads:[~2023-07-06 20:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  4:55 [PATCH v2 1/1] pcie: Add hotplug detect state register to cmask Leonardo Bras
2023-07-06  7:37 ` Juan Quintela
2023-07-06 17:58   ` Leonardo Bras Soares Passos
2023-07-06 14:35 ` Peter Xu
2023-07-06 18:07   ` Leonardo Bras Soares Passos
2023-07-06 18:14     ` Peter Xu
2023-07-06 18:37       ` Leonardo Bras Soares Passos
2023-07-06 18:50       ` Michael S. Tsirkin
2023-07-06 19:02         ` Peter Xu
2023-07-06 20:00           ` Michael S. Tsirkin
2023-07-06 20:17             ` Peter Xu [this message]
2023-07-10 17:49             ` Leonardo Bras Soares Passos
2023-07-10 18:16               ` Michael S. Tsirkin
2023-07-10 21:48                 ` Leonardo Bras Soares Passos
2023-07-06 21:47       ` Leonardo Bras Soares Passos

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=ZKchUNPG1mofzSOC@x1n \
    --to=peterx@redhat.com \
    --cc=leobras@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).