From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Jeff Moyer <jmoyer@redhat.com>,
Aarushi Mehta <mehta.aaru20@gmail.com>,
linux-block@vger.kernel.org, Julia Suvorova <jusual@mail.ru>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH liburing 0/4] spec: rpmlint fixes in preparation for Fedora packaging
Date: Sat, 3 Aug 2019 09:45:22 +0100 [thread overview]
Message-ID: <20190803084526.3837-1-stefanha@redhat.com> (raw)
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.
Stefan Hajnoczi (4):
COPYING: update to latest LGPL v2.1 text
spec: use Fedora "LGPLv2+" license identifier
spec: add URL tag
spec: fix <liburing/*.h> permissions
COPYING | 79 +++++++++++++++++++++------------------------------
liburing.spec | 5 ++--
2 files changed, 36 insertions(+), 48 deletions(-)
--
2.21.0
next reply other threads:[~2019-08-03 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 8:45 Stefan Hajnoczi [this message]
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 ` [PATCH liburing 0/4] spec: rpmlint fixes in preparation for Fedora packaging Jens Axboe
[not found] ` <20190805161411.GA10487@stefanha-x1.localdomain>
[not found] ` <20190808103254.GA3120@stefanha-x1.localdomain>
2019-08-08 16:13 ` 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=20190803084526.3837-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=jusual@mail.ru \
--cc=linux-block@vger.kernel.org \
--cc=mehta.aaru20@gmail.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).