From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org,
Jason Wang <jasowang@redhat.com>
Subject: [virtio-comment] Re: [virtio] Re: [PATCH] ccw: clarify device reset
Date: Fri, 26 Nov 2021 13:07:25 +0100 [thread overview]
Message-ID: <87sfvji0hu.fsf@redhat.com> (raw)
In-Reply-To: <20211027095847.27620882.pasic@linux.ibm.com>
On Wed, Oct 27 2021, Halil Pasic <pasic@linux.ibm.com> wrote:
> On Mon, 25 Oct 2021 09:34:02 +0200
> Cornelia Huck <cohuck@redhat.com> wrote:
>
>> > I can't remember they told me about moving it ;)
>> >
>> > I've found this one, and my guess is it works form the outside:
>> >
>> > https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=SA22720401
>>
>> Hm, this one is accessible; however, the 'view' link leads to the same
>> 500 again, and the 'download' link does not seem to do anything for me...
>
> I can confirm that the 'Read' link leads to the same dead-end. But
> download did work for me. I got a .boo file.
>
> I've contacted the guys who should be responsible for the above page.
> Maybe they can help fix the issue. Will let you know when/if something
> good happens.
As I've been looking at this thread again: Have you ever heard anything
back? The 'Read' link remains broken :(
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2021-11-26 12:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 11:38 [PATCH] ccw: clarify device reset Cornelia Huck
2021-10-12 2:54 ` Jason Wang
2021-10-12 11:16 ` [virtio] " Cornelia Huck
2021-10-13 6:20 ` Jason Wang
2021-10-13 7:01 ` [virtio] " Cornelia Huck
2021-10-21 16:23 ` Cornelia Huck
2021-10-21 23:35 ` Halil Pasic
2021-10-25 1:29 ` Jason Wang
2021-10-25 7:36 ` Cornelia Huck
2021-10-25 7:34 ` Cornelia Huck
2021-10-27 7:58 ` Halil Pasic
2021-10-27 8:02 ` Jason Wang
2021-10-27 9:16 ` Cornelia Huck
2021-10-27 22:25 ` Halil Pasic
2021-10-28 6:55 ` [virtio-comment] " Cornelia Huck
2021-11-26 12:07 ` Cornelia Huck [this message]
2021-11-26 17:11 ` Halil Pasic
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=87sfvji0hu.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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.