From: Maxim Levitsky <mlevitsk@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-trivial@nongnu.org,
Michael Tokarev <mjt@tls.msk.ru>,
Laurent Vivier <laurent@vivier.eu>, Max Reitz <mreitz@redhat.com>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] RFC: Trivial error message fixes for luks format
Date: Sun, 21 Jul 2019 21:15:06 +0300 [thread overview]
Message-ID: <20190721181508.28608-1-mlevitsk@redhat.com> (raw)
These are attempts to improve a bit error message
based on bunch of luks related bugzillas assigned to me.
Feel free to reject these if you think that it doesn't
make the messages better.
Best regards,
Maxim Levitsky
Maxim Levitsky (2):
LUKS: better error message when creating too large files
qemu-img: better error message when opening a backing file fails
block.c | 1 +
block/crypto.c | 25 +++++++++++++++++++++----
qemu-img.c | 2 +-
3 files changed, 23 insertions(+), 5 deletions(-)
--
2.17.2
next reply other threads:[~2019-07-21 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 18:15 Maxim Levitsky [this message]
2019-07-21 18:15 ` [Qemu-devel] [PATCH 1/2] LUKS: better error message when creating too large files Maxim Levitsky
2019-07-22 9:05 ` Daniel P. Berrangé
2019-09-12 22:44 ` Maxim Levitsky
2020-04-30 12:18 ` Maxim Levitsky
2020-04-30 13:03 ` Maxim Levitsky
2019-07-21 18:15 ` [Qemu-devel] [PATCH 2/2] qemu-img: better error message when opening a backing file fails Maxim Levitsky
2019-07-22 9:15 ` Daniel P. Berrangé
2019-07-22 10:01 ` [Qemu-devel] [Qemu-trivial] " Maxim Levitsky
2019-07-22 9:41 ` [Qemu-devel] " Kevin Wolf
2019-07-22 9:46 ` Maxim Levitsky
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=20190721181508.28608-1-mlevitsk@redhat.com \
--to=mlevitsk@redhat.com \
--cc=kwolf@redhat.com \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.