From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Steffen Einsle' <einsle@phptrix.de>
Cc: "win-pv-devel@lists.xenproject.org" <win-pv-devel@lists.xenproject.org>
Subject: Re: PV drivers 8.2.2. only testsigned?
Date: Mon, 4 Mar 2019 17:19:52 +0000 [thread overview]
Message-ID: <5073d4a5e9bf4508bfbb89d1ec625eb5__40362.06219332$1551764600$gmane$org@AMSPEX02CL02.citrite.net> (raw)
In-Reply-To: <2b0474b0-93dd-b66a-7858-b30a3cb3a671@phptrix.de>
Moving xen-devel to bcc and cc-ing win-pv-devel...
> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xenproject.org] On Behalf Of Steffen Einsle
> Sent: 04 March 2019 16:31
> To: xen-devel <xen-devel@lists.xenproject.org>
> Subject: [Xen-devel] PV drivers 8.2.2. only testsigned?
>
> Hi there,
>
> after downloading the drivers from
> https://xenproject.org/windows-pv-drivers/ I discovered that the 8.2.2.
> driverset is only testsigned - making it difficult to install and use
> them. I understand that signing is a complicated process and that
> development build drivers are always only testsigned - but the
> development build drivers are on the right side of the page and the
> 8.2.2. download is on the left. To me it seems to suggest "left side has
> release drivers with valid signing, right side has development builds
> with test signing"
Yes, normally we would not list a non-dev driver set here until they were signed. Not sure why that happened; they'd still be visible on xenbits.xen.org anyway but listing them along with signed sets is misleading. I'll try to get them removed until they have been signed.
>
> I just wanted to ask about any plans to release the 8.2.2. drivers with
> valid signing... or how the decision wether to sign or only to testsign
> is made...
>
The drivers normally stay test-signed until they have been properly tested and tagged. I will hopefully sign this set shortly.
Paul
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-03-04 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 16:31 PV drivers 8.2.2. only testsigned? Steffen Einsle
2019-03-04 17:19 ` Paul Durrant [this message]
2019-03-04 17:49 ` Wei Liu
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='5073d4a5e9bf4508bfbb89d1ec625eb5__40362.06219332$1551764600$gmane$org@AMSPEX02CL02.citrite.net' \
--to=paul.durrant@citrix.com \
--cc=einsle@phptrix.de \
--cc=win-pv-devel@lists.xenproject.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.