From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: virtualization@lists.linux.dev, jasowang@redhat.com,
xuanzhuo@linux.alibaba.com
Subject: Re: [patch virtio] virtio: delete vq in vp_find_vqs_msix() when request_irq() fails
Date: Thu, 9 May 2024 08:40:19 -0400 [thread overview]
Message-ID: <20240509083909-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <Zjy7g0diPulvEnae@nanopsycho.orion>
On Thu, May 09, 2024 at 02:03:15PM +0200, Jiri Pirko wrote:
> Hi, I'm new in sending patches to virtio tree directly. Do I need to do
> anything more in order to get this fix applied?
>
> Thanks!
I never had patches with "patch" in lowercase so missed it ;)
Queued now and I'd prefer [PATCH virtio] in the future.
Thanks!
next prev parent reply other threads:[~2024-05-09 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 15:08 [patch virtio] virtio: delete vq in vp_find_vqs_msix() when request_irq() fails Jiri Pirko
2024-04-28 1:16 ` Xuan Zhuo
2024-05-09 12:03 ` Jiri Pirko
2024-05-09 12:40 ` Michael S. Tsirkin [this message]
2024-05-09 13:29 ` Jiri Pirko
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=20240509083909-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=jiri@resnulli.us \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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).