From: Richard Henderson <richard.henderson@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Canokeys.org" <contact@canokeys.org>,
Gerd Hoffmann <kraxel@redhat.com>,
"Hongren (Zenithal) Zheng" <i@zenithal.me>
Subject: Re: [PULL 0/2] Misc next patches
Date: Wed, 26 Jul 2023 09:22:20 -0700 [thread overview]
Message-ID: <2915d99d-18de-4d02-8efc-0c6bf2091071@linaro.org> (raw)
In-Reply-To: <20230725162304.156157-1-berrange@redhat.com>
On 7/25/23 09:23, Daniel P. Berrangé wrote:
> The following changes since commit a279ca4ea07383314b2d2b2f1d550be9482f148e:
>
> Merge tag 'pull-target-arm-20230725' ofhttps://git.linaro.org/people/pmaydell/qemu-arm into staging (2023-07-25 12:44:39 +0100)
>
> are available in the Git repository at:
>
> https://gitlab.com/berrange/qemu tags/misc-next-pull-request
>
> for you to fetch changes up to 095be0910b89b5d156e20641bd65ac6cab3f8305:
>
> hw/usb/canokey: change license to GPLv2+ (2023-07-25 17:15:59 +0100)
>
> ----------------------------------------------------------------
> Miscellaneous fixes
>
> * Switch canokey device license from Apache to GPLv2+
> * Fix uninitialized variable warning in LUKS code
Applied, thanks. Please update https://wiki.qemu.org/ChangeLog/8.1 as appropriate.
r~
next prev parent reply other threads:[~2023-07-26 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 16:23 [PULL 0/2] Misc next patches Daniel P. Berrangé
2023-07-25 16:23 ` [PULL 1/2] crypto: Always initialize splitkeylen Daniel P. Berrangé
2023-07-25 16:23 ` [PULL 2/2] hw/usb/canokey: change license to GPLv2+ Daniel P. Berrangé
2023-07-26 16:22 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-25 16:24 [PULL 0/2] Misc next patches Daniel P. Berrangé
2023-07-25 19:11 ` 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=2915d99d-18de-4d02-8efc-0c6bf2091071@linaro.org \
--to=richard.henderson@linaro.org \
--cc=berrange@redhat.com \
--cc=contact@canokeys.org \
--cc=i@zenithal.me \
--cc=kraxel@redhat.com \
--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).