From: Jens Axboe <axboe@kernel.dk>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
Aarushi Mehta <mehta.aaru20@gmail.com>,
linux-block@vger.kernel.org, Julia Suvorova <jusual@mail.ru>
Subject: Re: [PATCH liburing 0/4] spec: rpmlint fixes in preparation for Fedora packaging
Date: Sat, 3 Aug 2019 07:25:11 -0700 [thread overview]
Message-ID: <1ecc837f-6177-c0a9-2d29-13efd29faf28@kernel.dk> (raw)
In-Reply-To: <20190803084526.3837-1-stefanha@redhat.com>
On 8/3/19 2:45 AM, Stefan Hajnoczi wrote:
> This series addresses the remaining rpm issues that I'm aware of.
>
> Jens: Once the patches are merged and you publish a 0.1 release tag I could
> roll the first liburing rpm for Fedora. liburing itself is in good shape for
> wider consumption but maybe it makes sense to wait for kernel issues to settle.
> There are qemu-iotests failures that are probably kernel bugs (hopefully known
> ones!) and will be investigated soon.
Applied all 4, thanks.
Any pointers to the qemu-iotests failures?
--
Jens Axboe
next prev parent reply other threads:[~2019-08-03 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 8:45 [PATCH liburing 0/4] spec: rpmlint fixes in preparation for Fedora packaging Stefan Hajnoczi
2019-08-03 8:45 ` [PATCH liburing 1/4] COPYING: update to latest LGPL v2.1 text Stefan Hajnoczi
2019-08-03 8:45 ` [PATCH liburing 2/4] spec: use Fedora "LGPLv2+" license identifier Stefan Hajnoczi
2019-08-03 8:45 ` [PATCH liburing 3/4] spec: add URL tag Stefan Hajnoczi
2019-08-03 8:45 ` [PATCH liburing 4/4] spec: fix <liburing/*.h> permissions Stefan Hajnoczi
2019-08-03 14:25 ` Jens Axboe [this message]
[not found] ` <20190805161411.GA10487@stefanha-x1.localdomain>
[not found] ` <20190808103254.GA3120@stefanha-x1.localdomain>
2019-08-08 16:13 ` [PATCH liburing 0/4] spec: rpmlint fixes in preparation for Fedora packaging Jens Axboe
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=1ecc837f-6177-c0a9-2d29-13efd29faf28@kernel.dk \
--to=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=jusual@mail.ru \
--cc=linux-block@vger.kernel.org \
--cc=mehta.aaru20@gmail.com \
--cc=stefanha@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).