From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/1] Block layer patches for 2.4.0-rc2
Date: Mon, 20 Jul 2015 16:54:57 +0200 [thread overview]
Message-ID: <1437404098-385-1-git-send-email-kwolf@redhat.com> (raw)
The following changes since commit 71358470eec668f5dc53def25e585ce250cea9bf:
Merge remote-tracking branch 'remotes/amit-virtio-rng/tags/vrng-2.4' into staging (2015-07-17 15:22:45 +0100)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to bd09594603f1498e7623f0030988b62e2052f7da:
crypto: Fix aes_decrypt_wrapper() (2015-07-20 13:35:45 +0200)
----------------------------------------------------------------
Block layer patches for 2.4.0-rc2
----------------------------------------------------------------
Kevin Wolf (1):
crypto: Fix aes_decrypt_wrapper()
crypto/cipher-nettle.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2015-07-20 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 14:54 Kevin Wolf [this message]
2015-07-20 14:54 ` [Qemu-devel] [PULL 1/1] crypto: Fix aes_decrypt_wrapper() Kevin Wolf
2015-07-20 16:00 ` [Qemu-devel] [PULL 0/1] Block layer patches for 2.4.0-rc2 Peter Maydell
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=1437404098-385-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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 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).