From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Longpeng(Mike)" <longpeng2@huawei.com>,
jasowang@redhat.com, pbonzini@redhat.com,
arei.gonglei@huawei.com, yechuan@huawei.com, eperezma@redhat.com,
alex.williamson@redhat.com, mtosatti@redhat.com, clg@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH v1 3/3] virtio-pci: defer to commit kvm irq routing when enable msi/msix
Date: Tue, 28 Feb 2023 07:29:42 -0500 [thread overview]
Message-ID: <20230228072616-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <Y/3gaVgDcf26vo6Y@redhat.com>
On Tue, Feb 28, 2023 at 11:07:21AM +0000, Daniel P. Berrangé wrote:
> IMHO it is not appropriate to criticize the writing of people
> who may not have English as a first language.
Sorry if I offended anyone. I do want change log messages to be clear
and unambigous though since they are a permanent record. Me rewriting
them for contributors does not seem to scale. I was hoping a grammar
checker will help but if not I don't know what to suggest then.
--
MST
next prev parent reply other threads:[~2023-02-28 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:39 [PATCH v1 0/3] virtio-pci: optimize set_guest_notifier Longpeng(Mike) via
2023-02-28 9:39 ` [PATCH v1 1/3] virtio-pci: submit msi route changes in batch Longpeng(Mike) via
2023-02-28 10:17 ` Michael S. Tsirkin
2023-02-28 11:20 ` longpeng2--- via
2023-02-28 11:39 ` longpeng2--- via
2023-02-28 12:09 ` Michael S. Tsirkin
2023-02-28 10:18 ` Michael S. Tsirkin
2023-02-28 11:24 ` longpeng2--- via
2023-02-28 9:39 ` [PATCH v1 2/3] kvm-irqchip: use KVMRouteChange API to update msi route Longpeng(Mike) via
2023-02-28 9:39 ` [PATCH v1 3/3] virtio-pci: defer to commit kvm irq routing when enable msi/msix Longpeng(Mike) via
2023-02-28 10:40 ` Michael S. Tsirkin
2023-02-28 11:07 ` Daniel P. Berrangé
2023-02-28 12:29 ` Michael S. Tsirkin [this message]
2023-02-28 13:05 ` Daniel P. Berrangé
2023-02-28 11:10 ` longpeng2--- via
2023-02-28 11:36 ` Michael S. Tsirkin
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=20230228072616-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=longpeng2@huawei.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yechuan@huawei.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).