From: Sachin Sant <sachinp@linux.ibm.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: linux-next@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kvm@vger.kernel.org
Subject: Re: [5.19.0-next-20220811] Build failure drivers/vdpa
Date: Thu, 11 Aug 2022 17:14:34 +0530 [thread overview]
Message-ID: <7137A7BC-1036-49A3-885B-FEBC7985871F@linux.ibm.com> (raw)
In-Reply-To: <CAGxU2F5V-qxurLSZhugvNLWkiDOM83tgKQrEUFB_PLd7=kTH3Q@mail.gmail.com>
> On 11-Aug-2022, at 3:45 PM, Stefano Garzarella <sgarzare@redhat.com> wrote:
>
>> Date: Wed Aug 10 11:43:47 2022 +0200
>> vdpa_sim_blk: add support for discard and write-zeroes
>>
>
> Thanks for the report, I already re-sent a new series with that patch fixed:
> https://lore.kernel.org/virtualization/20220811083632.77525-1-sgarzare@redhat.com/T/#t
Thanks. That patch works for me.
- Sachin
prev parent reply other threads:[~2022-08-11 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 10:06 [5.19.0-next-20220811] Build failure drivers/vdpa Sachin Sant
2022-08-11 10:15 ` Stefano Garzarella
2022-08-11 11:44 ` Sachin Sant [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=7137A7BC-1036-49A3-885B-FEBC7985871F@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sgarzare@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).